The Quest for Performance: Improve re-sampling implementation in Base

[eclipse-viatra-bot]

| --- | --- | | Bugzilla Link | 423491 | | Status | NEW | | Importance | P3 enhancement | | Reported | Dec 07, 2013 04:33 EDT | | Modified | Apr 11, 2016 05:45 EDT | | Version | oldinquery | | Depends on | 488439 | | Reporter | Abel Hegedus |

Description

In the current implementation (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=422775), EClasses that have derived features which must be re-sampled are registered through the NavigationHelper API, while it would be possible to simply add them to the list of observed types when it is the first time we traverse such an instance.

Additionally, the re-sampling uses the valueToFeatureToHolder table, but uses it in the feature -> holder -> value order. This might be improved in several ways, one-time cost would be the construction of the holderToFeatureToValue table, that is built on-demand.

[eclipse-viatra-bot]

By Istvan Rath on Apr 08, 2014 18:02

Moving this feature to post-0.8.

[eclipse-viatra-bot]

By Istvan Rath on Apr 24, 2014 04:30

This issue will surely be addressed at some point.

[eclipse-viatra-bot]

By Zoltan Ujhelyi on Mar 17, 2016 08:58

Could you look at these? Have fun. :)

[eclipse-viatra-bot]

By Abel Hegedus on Apr 07, 2016 08:25

Reversed dependency direction, since the other is a bug, this one is the enhancement.