> 2) There is something strange going on with Splay GGC. We could be much > faster on it. It seems like we are stuck in baseline on splay.js:49 for a lot > of time! That function is doing nothing but returning a value, but somehow > that takes 25% of the execution time (excluding gc). I guess something bogus > is happening there. We don't have this issue on Non-GGC branch
splay generates a tree and then does some operations on it. I bet that line is part of the tree generation, in which case it's called many times. > 7) Code-load runs only in interpreter/baseline. I think that is normal? Can > someone confirm? Sounds reasonable. Code-load is meant to be about parsing and (initial) compilation speed. Nick _______________________________________________ dev-tech-js-engine-internals mailing list dev-tech-js-engine-internals@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
