Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Papyrus/Oxygen Work Description/Refactoring/PerformancesImprovements"
| Line 1: | Line 1: | ||
| − | 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 1: Open a model (with many diagram already opened) | ||
| Line 6: | Line 10: | ||
Use Case 4: Drop an element from the model explorer (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 5: Change the selection with the property view open | ||
| + | |||
| + | == Tasks: == | ||
| + | ==== Task 1.==== | ||
| + | Setting up a continuous scalability evaluation [https://en.wikipedia.org/wiki/Testbed testbed] for Papyrus. | ||
| + | This testbed will be based on [https://eclipse.org/rcptt/ RcpTT] tests and [https://hudson.eclipse.org/papyrus/ 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 | ||
Revision as of 09:39, 9 November 2016
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
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