|Product:||WebKit||Reporter:||Eric Seidel (no email) <eric>|
|Severity:||Normal||CC:||darin, eric, ggaren, ian, mjs|
|OS:||OS X 10.4|
|Bug Depends on:|
Description Eric Seidel (no email) 2006-04-09 22:46:17 PDT
ggaren and I got a little carried away last weekend and well... implemented treecode. <rdar://problem/4409156>
Comment 1 Eric Seidel (no email) 2006-04-09 22:50:14 PDT
Comment 2 Eric Seidel (no email) 2006-04-10 00:11:48 PDT
FYI: on my MacBookPro the current numbers show nearly a 50% performance regression. Again, there is a lot of fat left to trim. % compare-timing-files -c 5 old.times latest-treecode.times ===== old.times ===== average of fastest 5 runs: 726.8 range of fastest 5 runs: 0.69% (5) ===== latest-treecode.times ===== average of fastest 5 runs: 1052.2 range of fastest 5 runs: 0.38% (4) performance LOSS of 44.77% (325.4 / 726.8)
Comment 3 Geoffrey Garen 2006-04-10 07:13:56 PDT
In some unit tests, the current numbers are only a 2% regression. It's likely that the js-ibench numbers reflect the fact that we haven't integrated function calls yet, so a function call starts up a nested version of the interpreter loop.
Comment 4 Darin Adler 2006-04-13 01:01:24 PDT
Comment 5 Cameron Zwarich (cpst) 2008-06-08 20:45:41 PDT
We did this with SquirrelFish.