|Re: Performance on Query Legacy with Sirius 6.1.0 [message #1806778 is a reply to message #1806745]
||Wed, 15 May 2019 06:54
|| Pierre-Charles David
Registered: July 2009
As its name implies, "Query Legacy" is not supported. Actually, it has never been officialy supported since Sirius has been released as Sirius, and was only there as a compatibility shim. Note that starting from Sirius 6.2, it will not work at all anymore (the IInterpreter APIs have changed in incompatible ways, and Query Legacy will not be adapted to the change). The recommended language to use for your expressions since Sirius 3.1 is AQL: https://www.eclipse.org/sirius/doc/specifier/general/Writing_Queries.html#aql
Concerning your particular issue, this looks a lot like a (known) side-effect of the change made in https://bugs.eclipse.org/bugs/show_bug.cgi?id=465576, 4 years ago. The change was especially to invert the lookup order to look for compiled classes before .mt scripts, as in Capella (before 1.3 which fully switched to AQL), the Query Legacy expressions used a lot of Java services but no .mt scripts. There is a preference (look in org.eclipse.sirius.query.legacy/src/org/eclipse/sirius/query/legacy/preferences/AcceleoPreferenceConstants.java) to revert to the previous lookup order, but be aware that if your modeler is based on / using Capella before 1.3, reversing the order may improve the performance on your own expressions but degrade the performance of the rest of Capella.
Again, switching to AQL + Java services is the recommended way: it is much faster, safer, and supported.
Pierre-Charles David - Obeo
Need training or professional services for Sirius?
Powered by FUDForum
. Page generated in 0.01443 seconds