We are always looking to improve performance, and with R37 much work has been done. Here is a quick summary. Many of the optimizations are resulting in 40-90% faster performance times!


Grids

The <Grid> tag  now includes an optional optimized attribute which defines whether or not each cell value, e.g., in TextColumn and ItemAttributeColumn, will be recalculated as needed or not. We have seen speed improvements of a factor 10 using this option and, therefore, recommend its use if a grid is slow. 


<Grid optimized="">

Valid values are "true" or "false". Default value is "false".


True: Each value will only be calculated once when you are working in the grid. This is suitable if the grid is for obtaining a "snapshot" that will be exported to Excel, etc. Grid generation and export times are optimized when set to "true" so Architects should consider using this optimization wherever possible. To refresh/recalculate the grid cell values at any time during viewing, hit F5.


False: Each value is recalculated as needed when you are working/editing in the grid. This is suitable if you always want the values to be updated. Grid generation and export times will include obtaining all relevant up-to-date values from the database.


The optimized response times can be seen in: 

  • Loading the grid
  • Scrolling in the grid
  • Exporting to Excel

Issue Iterations

If you use Iterations in your projects, you'll see that we have optimized the issues views when many iterations exist in the project.



Mirror Server

We have optimized part handling by the mirror server which results in improved mirror performance. The optimization will be most noticeable in larger, high-load installations.


Reports: Path Query optimizations

Various optimizations, primarily to increase the performance of reports that contain numerous path queries, e.g., 


Structure Tree

The loading of Simple parts in the structure tree has been significantly optimized.


In doing this optimization, we also changed the initial view setting for item structures. Previously, a Default structure tree setting of all structural parts along with a fixed list of legacy part types was loaded for new item types or for item types where items of that type are yet to be created. This has now been removed. When opening an item of a new or unused item type for the first time, users will not see any part types by default. Architects will need to set up the needed Default view. 







ISSUE ID: 15096, 15310, 15371, 15197, 15191, 15135, 15015, 15321