By aalmiray
via shemnon.com
Published: May 04 2008 / 20:19
I kind of brushed over Alex's speed improvements in the recent Groovy 1.6-beta1 release, but based on some recent benchmarks it looks like it needs some re-iterating. Alex implemented something called call site caching. Here's what goes on. When we encounter a call site we look at some notes we left the last time we ran through it, (assuming there are any). We compare notes, and if nothing changed, we don't recalculate the MOP dispatch and just do what we did last time. If our notes are different, we do the full MOP dispatch over again. It's the 'memento' design pattern....
Comments
jtheory replied ago:
Completely OT, but why does Moveable Type actively highlight the typo in the published post? That's just weird:
<span class="misspelt">suprised</span>
mikkelg replied ago:
Wow, somewhere between a 5-7.5% performance increase in the best of cases! The title is a bit sensationalist for these very small numbers, eh?
IMHO, performance is not something that should be focused on when talking about JVM based approaches. Acceptance into the enterprise, ease of writing extensions, and the massive amount of libraries available far outweigh performance gains.
,
Voters For This Link (16)
Voters Against This Link (3)