Performance/Status Meetings/2007-November-07
From MozillaWiki
Contents
Participants
Agenda
- AI's
- Infrastructure items
- Q4 Goals
- Gecko
Action Items
-
AI:alice-
StandaloneTalos - looking for feedback, done for now
-
- AI:schrep
- talk to linux vendors about native theme painting performance
- Coop changed talos to accommodate, so now doing performance test runs again.
- AI: justin
- need to follow up with johnathan re: bug 400045
- resolution from pav - need to move off colo machines hardware, seen this before
- going to watch numbers next week and pav to look for checkin that fixed it
- alice to look for "high number reporting" issue
- AI: bsmedberg
- ben to build current mini's (has access)
- moz2 buildbot stuff
- AI: justin
- justin to stock up on minis - ordering 50, only for perf
- IT to build and image, and if possible, get on tree
- AI: Alice
- get in each OS ready to be imaged for new minis
- no mac, vista or leopard - alice to create a mac image
- justin to bring up 2 machines, mac image coming next week, vista image a few weeks out
Infrastructure
- Moz2 mini farm implementation
- number of machines -
- 18 machines for trunk & branch
- plan to roll them out
- IT to take images and roll them out.
- bhearsum is going to be working primarily in Build for the next 1-2 months.
- Will still be supporting the existing Talos machines
- Working on Try server Talos, Vista slaves, baselines is on the back burner for now.
- Discussion over Talos/Tbox stability
- Much more stable - planned to add the tests to the production tree in 1 month (11/3)
-
blocked on bug 393338 - xml parsing bug re: svg - leaving this test off as it's unstable
- initial setup done, changes, very close
- pushing out to 11/14
- Talos on the try server bug 398192
- The Buildbot side is moving quickly, I've already run a couple of test slaves.
- Managing/interpreting the data will take longer to figure out.
- robcee has machines and passwords, pushed off for production perf stuff
- punt for 2-3 weeks due to other priorities
- Leak/Mochi tests on debug builds
- coop's item
- tracking bugs: bug 397724,
bug 374822, bug 397725 - blocked on machines
- Talk about the happenings on the tree wrt bug 400045
- Ben/Robcee to look at numbers
- still not resolved, justin to follow up
- pav says numbers are back to normal - resolved?
- js test integration into talos
- crashing the browser
- Goals for q4
- Agreed goals:
- stable production talos for branch trunk (4 platforms) on tree
- perf enabled try server
- stand alone talos box
- baselines for historical numbers
- graph server improvements (perhaps seneca)
- investigate (rock) performance solutions for mobile
- Bring up new tinderboxen to run leak and mochi tests on debug builds.
- Agreed goals:
Gecko: Perf discussion
- Perf Bugs for FF3:
- 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)
- dtrace status
- in, use --enable-dtrace on Solaris and Leopard.
- need to figure out how we're going to ship this (is it enough to build with the header file on 10.4, or do we actually need 10.5's compile-time linker?)
- Followups
- sessionStore is really slow -- bug 398807 -- checked in, remaining issues marked blocking-, does this need to be tracked any more?
- waiting for native json serializer to land
- force cycle collection in between page load in talos (bug # needed)
- TODO: vlad -- figure out what's going on there (with jonas)
- sessionStore is really slow -- bug 398807 -- checked in, remaining issues marked blocking-, does this need to be tracked any more?
- Firefox front-end perf
- sayer to put list of tasks on wiki
- focus on measurements on tabbrowser reduction
- Performance:FrontEnd
- dolske will do some profiling work
- sayer to put list of tasks on wiki
- On radar
- 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
- others?