Performance/Status Meetings/2007-December-19

From MozillaWiki
Jump to: navigation, search

« Back to Status Meetings

Leaks

Fragmentation

  • Smaug's patch for content object in bug 403830 landed. Showing perf wins, but memory-high (MH) increased by 300K. Got some of it back in bug 408720 but a lot remains still, largely for unknown reasons.
  • Layout churning has been improved.
  • Working on removing allocations where it makes sense
    • Significant progress in last few weeks.
    • JS still allocation happy -- Stuart/crowder/brendan/igor looking at this.

Status on found leak bugs

  • Tomcat has done more litmus testing and filed a set of new bugs.
    • Litmus tracker is bug 402335.
    • Lots of these leak windows and documents which means we'll leak a lot of other objects too.
    • bug 408612 and bug 408689 are extension leaks, though possibly not bad ones (shutdown leaks). Might affect other extensions too.
    • The bad news is that we have a lot of bad chrome leaks. The good news is that these leaks are unlikely to accumulate over time as the user is unlikely to perform the leaking operation many times (e.g. run session restore, configure toolbar, etc).
    • Should still look into these to see if it's a smaller set of platform bugs causing many of these.
    • bug 398219 might fix a few of them.
  • Jonas ran mochitest and reftests while logging leaks.
    • Tracker is bug 408905.
    • Only one real leak in all of reftest, and it has a patch! bug 408883
    • Mochitests show a few more, but only one really bad bug 408927
    • Need to get automated testing going and reported to main tinderbox. bug 397724. Coop working on it but could use help.
  • Other bad, or potentially bad, leaks are:
    • Editor leaks elements, bug 407072. Has patch, awaits review.
    • Liveconnect leak, bug 396368. Should be fixed by new java plugin, but need to test this fact. If we want to fix before then we need help from sun.
    • Leaked windows in bug 403862, but lacks proper steps to reproduce.

Fixed bugs

  • 8 leaks resolved since last week. [1]
    • 3 bugs fixed.

Action Items

  • AI:sicking Look into enabling trace-refcount, without the tracing part in nightlies.
  • AI:cbarrett Look into OS leaks on Mac.
  • AI:dbaron Make assertions fatal on new windows leak box.
  • AI:sicking Test leaked handles on windows manually using purify.
  • AI:sayrer Run leak buster while looking for trace-malloc leaks.
  • AI:sicking to go through and prioritize leak bugs

Perf (speed) discussion

  • Txul platform differences according to mac mini machines
    • mac: slowest on 1.8, slower still on 1.9 (30% regression)
    • windows: fastest on 1.8, now in second place (30% regression)
    • linux: middle on 1.8, now fastest on 1.9 (30% improvement)
  • massive Ts regression in 2006
    • Related to thread manager landing
    • [AI:vlad] looking for an owner, will talk to Damon
  • Firefox front-end perf
    • sayer to put list of tasks on wiki
    • dolske will do some profiling work


  • On radar (unowned stuff that people have mentioned have mentioned we should look at at some point)
    • Stuart's page-out/page-in tests?
    • Theme optimization
    • roc's scrollbar issues
    • startup performance (fastload perf, loading libXUL and other files, etc.) (unowned)
    • more work to speed up onSecurityChange, but further work will require SSL work and reducing the number of notifications
Retrieved from "https://wiki.mozilla.org/index.php?title=Performance/Status_Meetings/2007-December-19&oldid=78376"