Page History
Content layer | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Content block |
Anchor | Performance | Performance | Performance ImprovementsProject Merge ImprovementsProject Merge has undergone considerable performance improvements. Modeling tool version 20.0 requires 3-4 times less memory to successfully merge two server project branches compared to 19.0 SP4. A chart comparing merge memory consumption in different modeling tool versions.Furthermore, the merge speed has increased by 20-70% in 20.0 compared to 19.0 SP4. Charts comparing merge performance in speed and memory modes.TWC Project Load Memory and Speed ImprovementsProject load memory and speed improvements have been implemented for Teamwork Cloud. The modeling tool now requires only 2GB of heap to load a project (first and second time) when working with TWC projects compared to 8GB in 19.0 SP4. Additionally, as a result of the UML metamodel changes mostly, SysML projects are now opened 2-3 times faster. N.B Received results cover the project load only, excluding validation, diagramming, and further modeling tool feature usage. N.B A red border on a bar chart in the image below indicates a low memory occurrence during testing. Charts comparing load memory and speed improvements between different modeling tool versions.
TWC Disk Footprint ImprovementsMajor TWC disk footprint-related changes are presented in this release. TWC 20.0 requires twice as less disk space for the same amount of projects with no history compared to TWC 19.0 SP4. In addition to this achievement, the disk size growth is cut nearly 5 times in TWC 20.0 compared to TWC 19.0 SP4 for those projects users work actively on. A chart comparing TWC disk footprint between different modeling tool version
Partial Data Loading in TablesExperience enhanced table loading and scrolling performance! Thanks to the newly-introduced Load Partial mode, data is now loaded in only visible rows, meaning that there is no need to wait until data is calculated in the entire table. What is more, fast scrolling has improved – it is now considerably smoother. A chart comparing the opening time of Requirement Table having 7 standard columns with a different number of requirements.Learn more about partial loading in tables >> Enhanced Copying/Pasting Operation SpeedRecent modeling tool performance improvements have led to an increase in the copying/pasting operation speed. Now you can copy and paste data noticeably faster for maximized productivity. A chart comparing the copy&paste operation time in various scenarios.Profiling Changes in the UML 2.5.1 MetamodelSignificant changes have been implemented to the UML metamodel for performance reasons. The InstanceSpecifications, Slots, and ValueSpecifications are no longer used to store profiling data. Instead, new model element types and properties are introduced while some have been removed (see the diagram below). Profiling changes in the UML metamodel.As shown in the figure above, Element references the TaggedValue that is used to specify the Boolean, Integer, Real, String, or Element values of the applied stereotype properties. This approach uses fewer model elements to store profiling data, which leads to a decrease in the total number of elements in SysML and UAF projects by 40-80%. N.B Expressions based on the previously implemented profiling data storing metamodel no longer work, meaning that they have to be updated manually.
|