Re: Question about Pattern.matcher performance differences between
Java6 and Java7/8
On 26.12.2013 02:24, Stefan Ram wrote:
Kevin McMurtrie <mcmurtrie@pixelmemory.us> writes:
Neither can determine real GC load. What ends up happening is that yo=
u
pull a chunk of suspect code out of your app and run it by itself in a=
controlled environment to benchmark it. The alternative is using a
Sometimes, one wants to compare two versions of suspect code,
one of which has some new =BBoptimization=AB, to see whether that
optimization helps indeed as much as hoped for.
When one needs to optimize, the application must be observably
slow. That means: macroscopically slow, so slow that one can
measure it using a stop watch or at least detect he slowness
somehow.
In this case, one can compare the two versions in-place. That is:
run the app with the old version and then with the new version.
This will include =BBreal GC load=AB and all.
I'm not sure I agree to the "real GC load": if you artificially slow the =
application down to a level where you can use a stop watch you have
already changed behavior dramatically and all bets are off.
Or did you mean it the other way round: you can only apply the stop
watch approach if the application is so slow?
Kind regards
robert