|Re: java_trace files necessary? [message #1767925 is a reply to message #1767823]
||Wed, 12 July 2017 08:23
| Zoltan Ujhelyi
Registered: July 2015
first of all, we are sorry that code generation is slow for your use case. We are already actively working on this area, and have already a few profiling sessions to identify the cause of slowness. Interestingly, the progress monitor display and the profiling results does not feel entirely in sync, so we are very careful of pointing at the generation of some specific files is the main culprit or not. Generating the java_trace files is one candidate to turn off, however, we did not find an easy to do yet.
Nonetheless, given we have already identified a few cases that affect the code generation performance, based on them I try to offer at least some workarounds until we have a better solution:
* If your metamodels are only available in your workspace or your target platform
* Installing the metamodels into the host Eclipse should result in faster code generation. This is especially true, if you have large genmodel files that are used for multiple EMF metamodels (e.g. subpackages).
* If you cannot install these metamodels, you could turn on our experimental switch in the Eclipse preferences on VIATRA preference page VIATRA Tooling; this turns on a cache of known metamodels that is known to speed up the generation. However be careful that if your metamodel changes, this cache will become invalid. This feature is available since VIATRA 1.5.2.
* If you are using an antivirus software (including Windows Defender), it helps to turn its live validation off for the workspace folder. We have seen this causing serious performance issues.
Powered by FUDForum
. Page generated in 0.02397 seconds