|
| Re: Epsilon profiling tools missing? [message #986664 is a reply to message #986474] |
Wed, 21 November 2012 10:33   |
|
One thing you should keep in mind regarding Epsilon performance is that all E*L languages are interpreted. You could get better performance writing everything in Java yourself, but the resulting code would be much less concise and changes would be more difficult.
ProfilerTool should be still available from the Epsilon Core Development Tools feature: it's in plugins/org.eclipse.epsilon.eol.tools/src/org/eclipse/epsilon/eol/tools/ProfilerTool.java in the SVN repository. It is defined inside the org.eclipse.epsilon.eol.tools project and referenced by the org.eclipse.epsilon.eol.dt.tools plugin.
According to the logs, ProfilerTool hasn't been changed since 2008, except for some commit in 2011 that added profiling to server-side EGL, which shouldn't interfere with EOL.
Could you send us a minimal example that reproduces the issue?
http://eclipse.org/epsilon/doc/articles/minimal-examples/
[Updated on: Wed, 21 November 2012 10:34] Report message to a moderator |
|
|
| Re: Epsilon profiling tools missing? [message #986709 is a reply to message #986664] |
Wed, 21 November 2012 11:56 |
 Joost van Pinxten
Messages: 51
Registered: November 2012 |
Member |
|
|
I do understand that E*L languages are interpreted and I don't think that 10x slower is that bad, but I would like to see if the profiling tool shows me what the expensive parts are, so that I can try to tune this when it gets out of hand and identify the bottlenecks, instead of guessing what the root cause is.
With the latest releases I reckon that instead of org.epsilon it should be org.eclipse.epsilon, but then the builtin package is not found (in a normal Java environment). Finally, org.eclipse.epsilon.eol.tools.ProfilerTool seems to be the correct location. However, I'm still unable to instantiate this from EGL via the standalone job. I've added the tools package to both the transformation plugin and the standalone plugin, but it is still not recognized as a type.
While making a minimal example, I created an EOL file with the content of the example in the pdf linked in the first post, but changed the native type to org.eclipse.epsilon.tools.ProfilerTool which does execute correctly for me. I will investigate why my standalone example (which uses the WorkspaceJobs as in the Epsilon Labs) does not recognize the type... It seems the job itself can actually properly instantiate the type.
So to answer my own question: yes, it has been moved, but that was only part of the problem apparently. Will follow up if my solution/actual problem is worth sharing.
|
|
|
| Re: Epsilon profiling tools missing? [message #986732 is a reply to message #986709] |
Wed, 21 November 2012 13:29 |
|
Hi Joost,
In your standalone setup you'll need to add the following line so that tools contributed via extensions (such as the ProfilerTool) can be used:
context.getNativeTypeDelegates().add(new ExtensionPointToolNativeTypeDelegate());
Cheers,
Dimitris
|
|
|
|
|
| Re: Epsilon profiling tools missing? [message #987120 is a reply to message #986846] |
Fri, 23 November 2012 15:50 |
Joost van Pinxten
Messages: 51
Registered: November 2012 |
Member |
|
|
Hi again,
You're welcome, thought I'd give something back to the community 
Today, I've come across the options to automatically profile an EOL file by setting the profile options in the run configuration. However, this does not mix with normal profiling calls (see bug #394975).
What I learned from profiling my transformation is that loading templates is costly; i.e. the time it takes to load a single template is longer than the time the original transformation used to process and write everything to disk. That's okay (and somewhat expected) though, now I'm just trying to work around this, by avoiding to reload templates from files.
Also, it seems (but I'm not sure) that the profiling information in an Eclipse session launched from Eclipse cannot be more precise than 10ms (most results are a multiple of 10), while in a normal Eclipse environment it seems to be accurate to 1ms. Is this perhaps a restriction for any Eclipse WorkSpaceJob?
On another note, I've just now added the fine-grained profiling to the transformation job by using:
module.getContext().getExecutorFactory().addExecutionListener(new ProfilingExecutionListener());
Thank you for your time,
Joost
[Updated on: Fri, 23 November 2012 15:52] Report message to a moderator |
|
|
| Re: Epsilon profiling tools missing? [message #987258 is a reply to message #987120] |
Sun, 25 November 2012 09:46 |
|
Hi Joost,
> Today, I've come across the options to automatically profile an EOL file by setting the profile options in the run configuration. However, this does not mix with normal profiling calls (see bug #394975).
Thanks for reporting this. I'll investigate.
> Also, it seems (but I'm not sure) that the profiling information in an Eclipse session launched from Eclipse cannot be more precise than 10ms (most results are a multiple of 10), while in a normal Eclipse environment it seems to be accurate to 1ms. Is this perhaps a restriction for any Eclipse WorkSpaceJob?
I don't think we treat the two environments differently but I'll need to double-check.
> Apparently the listener needs to be applied _AFTER_ the module has been parsed
This seems to be the case indeed. I'll investigate this too 
Cheers,
Dimitris
|
|
|
|
Powered by
FUDForum. Page generated in 0.04816 seconds
] 
Search
Help
Register
Login
Home
