|Re: XText builder run takes many minutes on eclipse start [message #981603 is a reply to message #977795]
||Mon, 12 November 2012 14:49
| Sven Efftinge
Registered: July 2009
itemis provides professional support services around Xtext and Eclipse
Modeling in general. We have a lot of experience in measuring and
optimizing performance and would be glad to help you.
Please send me an E-mail if you are interested in this kind of support
so we can discuss the details.
Am 11/9/12 4:44 PM, schrieb Dimitry Polivaev:
> I use XText for creating a DSL for test case generation. Generator
> scripts containing test strategies are created from our strategy mind
> maps as described in arxiv.org/abs/1202.6125v1 (you do not have to read
> the article :) ).
> The scripts can become pretty long (thousands of LOC). Some other script
> files are created directly in editor. We have created an XText based
> editor and debugger.
> With growing size of our script files (currently about 4000 lines) an
> eclipse start or refresh takes many minutes, and it is likely to become
> longer as our strategy maps continuously grow. I do not know how we
> could accelerate this process. We activate no backtracking.
> (Currently the scripts are compiled using a second parser based on
> JavaCC which does not have any problems with their size. The XText based
> solution should be used only for editing and debugging in Eclipse).
> Is there are someone who could have a look at our grammar definition and
> the parsed files and give us a hint how to improve the XText
> performance? I would provide the files but unfortunately I can not make
> them available directly in the forum.
> Dimitry Polivaev
> Test Architect
> System Test for EMV / ID Products and Mobile Security Secure Devices
> Giesecke & Devrient GmbH, Prinzregentenstr. 159, D-81677 Munich, Germany
Need professional support for Xtext or other Eclipse Modeling technologies?
Go to: http://xtext.itemis.com
Twitter : @svenefftinge
Blog : http://blog.efftinge.de
Powered by FUDForum
. Page generated in 0.22476 seconds