Performance of Dump Request

16 views
Skip to first unread message

Mario Ackerl

unread,
Sep 28, 2015, 5:07:22 AM9/28/15
to JaCoCo and EclEmma Users
Hello together,

currently I am looking for ways to increase the performance of our Project, if coverage of the junit tests is being collected. Unfortunately my measurement results show, that we spend nearly all of the time with requesting dumps.

For example: a suite with 60 Tests performing in 200 ms in an normal environment, takes 10,5 seconds in an environment, where code coverage is collected, but 10,25 seconds of that time were spent between:

ICoverage.requestDump
ISessionListener.sessionAdded


Is there a way to increase the performance of the dump? 

Best Regards

Mario

Marc R. Hoffmann

unread,
Sep 28, 2015, 11:27:02 AM9/28/15
to jac...@googlegroups.com
Hi Mario,

from the APIs you're refering to I assume you're talking about the EclEmma Eclipse plug-in, right?

Displaying coverage information within Eclipse needs two steps:

1) Requesting a execution data dump from the SUT JVM. This should typically take a few milliseconds
2) Analyzing the coverage session, which involves traversing all classes in your workspace depending on the session scope. Depending on the number of projects/classes in scope this may take up to a minute.

Not sure what time (1 or 2) you're exactly meassuring. But even if you meassure 1) the analysis might eat a lot CPU as new sessions are automatically activated. This can be disabled in the EclEmma preferences.

Regards,
-marc
--
You received this message because you are subscribed to the Google Groups "JaCoCo and EclEmma Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jacoco+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/723ae91c-d98d-4464-bd5b-1be09ed270b8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages