| [Epsilon] Performance [message #602069] |
Thu, 21 June 2007 04:33 |
Eclipse User |
|
|
|
Epsilon is quite slow on large models. Reason seems not to lie in
language interpreter itself, but in model access. Major cause is name
lookup in NameExecutor#execute. Every variable access first looks for
model elements (slow) only then in current variable scope. Looking up
variable first speeds things up by incredible amount. I wouldn't mind
variable-first semantics. Current (model-first) one should be enforced
by checking for name shadowing conflict before interpretation.
Another proposal: it would be nice that empty name model access always
accesses first registered model, even if more than one model is
registered. This way, scripts written for processing of single model
would still work on multiple model resource sets (I have several use
cases for this). This would also resembe how EMF editors work (first
resource is active one). It's a simple change in
EolModelRepository#getModelByName
-a
|
|
|
Powered by
FUDForum. Page generated in 0.03447 seconds
Home