|Re: [mdt-papyrus.dev] Model indexer patch|
Hi,Regarding the performance degradation, I would like to point out bug 517982 written on Papyrus-RT, where the performance degradation in the properties view is much more evident than in base Papyrus. But as indicated in that bug, the core issue can be seen in base Papyrus as well. And when the properties view becomes sluggish, everything else becomes sluggish since the update of the update of the properties view slows down most other operations that you do, like selecting and moving elements in diagrams./Peter CigéhnOn 9 June 2017 at 13:13, Ed Willink <ed@xxxxxxxxxxxxx> wrote:
From one point of view, my opinion does not matter since my usage of Papyrus is minimal and mostly concerned with checking OCL test models.
On the other hand, I may be one of very few users who actually use Papyrus 3.0 and so I may be revealing a real user problem.
My models are tiny, so if I have problems how will real users with big models cope?
As an observer, it appears that much too much late development has been going on. After M7 only important fixes, not new development. It's a pain, but stability and test is important. For both OCL and QVTd I held back developments that could not be ready. If it was clear at M7 that Papyrus 3.0 could not be ready for Oxygen, a 2.x maintenance release should have been announced and contributed. There is now no prohibition on Papyrus 3.0 being released as Oxygen.1.
As a user, it appears that Papyrus performance seems to have degraded significantly. Are there are any performance tests to contradict my suspicion? If I was using Papyrus actively I would certainly look to compare Luna/Neon/Oxygen in order to select one with an acceptable UI speed.
On 09/06/2017 09:49, LE MENEZ Quentin wrote:
As we still have time, although not that much, before RC4 and we all experienced some issues with this I would be inclined to merge it today and test Papyrus before Tuesday next.
Christian proposed a patch that seems to vastly improve the performance of the model indexer.
You can review it here 
Open question: do we merge it before RC4?
As far as I know, only Ed and I complained (a lot J) of this indexer.
Since we are only 2 and with more a developer profile,
the best way to go seems to merge it right AFTER RC4.
This way, we don’t take any risk, and Ed and I may switch to the nightly next week.
Any thoughts ?
_________________ mdt-papyrus.dev mailing list mdt-papyrus.dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailma n/listinfo/mdt-papyrus.dev
mdt-papyrus.dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
Back to the top