Dear Hana,
first of all, sorry for not answering your direct email with the same topic, but I was out of office last week and I am a bit swamped with my tasks. In general, we recommend the Eclipse Forum for support questions, as this mailing list focuses
more on the development of VIATRA, while private emails might get postponed a bit.
—
Thanks for your kind words about VIATRA, it is nice to hear about it. I did not have time so far to have a deeper look at the transformation and the solution itself (and I’m afraid I will not have the time to do so this week), but in general,
our experience with large memory usage is that there are one or more patterns that represent a model structure that cannot be calculated without enumerating a cartesian product. Some things you could check:
1. Do you have any patterns that the VQL editor reports warnings for? These warnings find a lot of these cases that are problematic for memory usage.
2. If you don’t, you could try to use the QueryPerformanceTest implementation [1] to figure out which of the patterns have larger memory usage. If we know which pattern is problematic, it is usually easier to figure out what the issue is and
how it could be rewritten to be better.
Hope this was helpful,
Zoltán
Dear Viatra developers,
I am Hana Mkaouar, post-doctoral at Telecom Paris.
We are working on a benchmark based on the AADL language for incremental model transformation tools.
We used your VIATRA tool and we thank you for your quick response on the VIATRA forum ( https://www.eclipse.org/forums/index.php/m/1816028/#msg_1816028).
Also, we thank the maturity of your tool (good documentation, new publications, good performance of execution time).
We have now performed the evaluation of your tool (compared to eMoflon and MoTE tools) and we would like to have your opinion about the implemented solution and the results and observations ( https://gitlab.telecom-paris.fr/mbe-tools/mt-bench-public/-/tree/master/viatra).
We have a public GitLab ( https://gitlab.telecom-paris.fr/mbe-tools/mt-bench-public/-/tree/master/docs), where you can find the description of the model transformation
and the results.
An important point is that we do notice some memory issues (OutOfMemoryError) when using large models (detailed in docs/test-suite.pdf).
Could you please explain to us the reasons of this problem, is it due to our specifications or is it a current limitation of VIATRA that you are working on?
Do you propose some optimizations to improve the results?
Thank you,
Cordially,
Hana Mkaouar.
_______________________________________________
viatra-dev mailing list
viatra-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/viatra-dev
|