Mobile/Archive/Chrome JIT

Summary

JIT has much chrome UI as possible, and identify hot spots where we should be careful in the future. If possible we shoud create some test in these places to be sure we don't regress.

Current Status

Next Steps

• Push a patch to allow using tracevis on a per function basis
• Identify the "hot" places

Related Bugs

bug 518176

Team

Goals/Use Cases

• Prevent the trace to abort into the essentials functions
• Try to optimize the "hot" places (places where tracing abort, but also places where monitoring slow us down)

Non Goals

• Correct all the trace abort

Documentation

https://developer.mozilla.org/en/TraceVis

http://hacks.mozilla.org/2009/07/tracemonkey-overview/

http://blog.mozilla.com/dmandelin/2009/02/26/tracevis-performance-visualization-for-tracemonkey/

https://developer.mozilla.org/En/SpiderMonkey/Internals/Tracing_JIT