638
edits
JSThreadsAndGC: Difference between revisions
Jump to navigation
Jump to search
→Per-tab GC: link to existing gc benchmark bug
(→Per-tab GC: link to existing gc benchmark bug) |
|||
| Line 29: | Line 29: | ||
! scope="col" | Assigned to (guess) | ! scope="col" | Assigned to (guess) | ||
|- | |- | ||
| | | Benchmarks | ||
| | | 1? | ||
| jorendorff/gwagner | | jorendorff/gwagner | ||
|- | |- | ||
| Line 58: | Line 58: | ||
|} | |} | ||
''' | '''Benchmarks''' — In {{bug|548388}}, Gregor is building a GC benchmark suite. We need a way to turn a crank and get GC performance numbers from that. sayrer should get mail when we make these numbers move. This means we need to be able to measure GC performance in opt builds. Total time spent in GC and max pause time are cheap enough to collect. | ||
'''Compartments and wrappers API''' — Add API for creating a global object and associating it with a compartment. Use it in Gecko everywhere we create a global. Add minimal API for a special kind of object that is allowed to hold a strong reference across compartments (a wrapper object). Use it in XPConnect for our security wrappers. | '''Compartments and wrappers API''' — Add API for creating a global object and associating it with a compartment. Use it in Gecko everywhere we create a global. Add minimal API for a special kind of object that is allowed to hold a strong reference across compartments (a wrapper object). Use it in XPConnect for our security wrappers. | ||