> > I was saying accurate for "being sure that a particular trick is consistent", > reading the wiki you can think that (value*.5) is faster than (value/2) > (the flaw of the micro-benchmarks) but I think the code I showed earlier > prove it's not. >
just a little add up on that from that link http://strongtalk.org/benchmarking.html and the comment here http://blogs.sun.com/chrisoliver/entry/hotspot_vs_adobe_tamarin_vm " CrossPoster: Tamarin JITs all methods that might be called more than once. So you're seeing JITted performance for benchmarks that put the critical path code into a function, but: as noted early in this blog, without a package {} around the function, and type annotations, the JIT currently de-optimizes significantly. The empty package wrapping enables early binding, and the type annotations avoid "boxing" of runtime-type-tagged values in and out of the function. There may be other effects; perhaps Ed will comment again. Hence the significant speedup for the "Typed" versions of the tests. We will make "Untyped" code fast too, for all the "Web JS" out there. /be " 2 things - run tests in package and from within function - the other one being don't call trace() while calling your tests I 've been bite by this flaw the same as some exemple of the wiki cheers, zwetan _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
