Skip to main content
Jump to: navigation, search

Papyrus/Oxygen Work Description/Refactoring/PerformancesImprovements

< Papyrus‎ | Oxygen Work Description
Revision as of 07:15, 10 November 2016 by Benoit.maggi.gmail.com (Talk | contribs) (Use cases:)

Thanks to their experience on performances in modeling and their expertise on the VIATRA technology, IncQueryLabs contributes to the Oxygen release of Papyrus by: - Providing means to assess and monitor some performance critical use cases in Papyrus. - Improving the performances on some of these cases.

Use cases:

Use Case 1: Open a model (with many diagram already opened)
Use Case 2: Navigation in model explorer (Especially with stereotype with custom icons)
Use Case 3: Drop an element from the palette (Especially with a custom css)
Use Case 4: Drop an element from the model explorer (Especially with a custom css)
Use Case 5: Change the selection with the property view open
Use Case 6: Flat View in Select type widget
      - Create a model with many elements
      - Create a class with a property
      - Select the property and set the type in the property view
      - In the popup widget there is a tab named Flat (this tab presents all elements from the model and can be slow in big models)

Tasks:

Task 1.

Setting up a continuous scalability evaluation testbed for Papyrus. This testbed will be based on RcpTT tests and Hudson jobs

Its goal is to:

(i) highlight future regressions 
(ii) validate future enhancements

Task 2.

Identifying and sharing existing models (UML, notation, css, profile) related to performance bottlenecks in Papyrus. The Papyrus community is expected to share some models, but many performance issues are only present in big proprietary models (Obfuscation will probably be required)

Its goal is to:

(i) share a library of models that can be used for any kind of testing in Papyrus

Task 3.

Integrate a Papyrus specific indexing module based on the VIATRA base-indexer and query engine to improve model navigation and derived feature usage. Based on the 2 previous tasks, there will be an evaluation before and after the model integration to check performance improvements.

Links

To be completed:

- links to shared models
- links to RcpTT tests and Hudson performance jobs

Back to the top