|
Replies:
2
-
Pages:
1
-
:
Nov 14, 2020 6:45 AM
by: Jan
|
|
Posts:
2
From:
Germany
Registered:
|
|
|
|
New Metric: duration
Posted:
Nov 4, 2020 8:56 AM
|
|
|
If Clover would record the time needed for a code block, the history would automatically give a performance measure - especially combined with a set of performance JUnit-Tests.
|
|
|
|
Re: New Metric: duration
Posted:
Nov 4, 2020 5:51 PM
in response to:
|
|
|
Hi Jan,
Thanks for this suggestion. Unfortunately the instrumentation that Clover introduces to measure code coverage has some runtime performance impact, so that any timings that Clover recorded be only indicative. Clover can give some clues to performance by inspecting the "hit count" for each statement in the Clover report.
Regards,
-Brendan
|
|
Posts:
2
From:
Germany
Registered:
|
|
|
|
Re: New Metric: duration
Posted:
Nov 14, 2020 6:45 AM
in response to:
|
|
|
Changing the measures by Clover doesnt matter: both values (old and new run) are done by Clover so the difference is (nearly) the same and you got your result.
Main points are:
- where to spend time for tuning
- was the tuning successful
(profiling) And this done by a server (Gump, CruiseControl) automatically.
|
|
|
|
|
