Hi all, I was about to get a brand new assembly to ask some questions on the list here when I installed the newest available jdk7 update 6. I ran my simple Fibonacci test program and noticed that the time it took was sudden 4.6s, where it was 3.5s before. This plus 1s doesn't look too god to me. Has there been anything special that causes this? I mean before the indy version was a little faster than our call site caching, now it is a little slower. General java performance seems not to be reduced, so I would assume it is special to indy.
See http://rifers.org/paste/show/1702 ... so now... is there sombody who can tell me why my indy version is now even slower than my call site version? Sadly I am not really fit enough in assembler anymore, especially the one produced by hotspot to really read that output. So I have no idea what is wrong. Two things I should mention... the call to $getCallSiteArray is surplus, yes, but that doesn't take much time. The only thing I know that really takes a lot of time is the exception guard, but that I have to have until I find a way to avoid it.... and the call site version has both as well of course. They should not count as satisfying explanation. bye Jochen -- Jochen "blackdrag" Theodorou - Groovy Project Tech Lead blog: http://blackdragsview.blogspot.com/ german groovy discussion newsgroup: de.comp.lang.misc For Groovy programming sources visit http://groovy-lang.org _______________________________________________ mlvm-dev mailing list mlvm-dev@openjdk.java.net http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
