Breakpad/WorkWeek: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 18: Line 18:
**fs/os changes
**fs/os changes
**query tuning
**query tuning
****monitor
***monitor
****reports
***reports
****interactive query tuning
***interactive query tuning
******memory checks
****memory checks
**index/schema check
**index/schema check
**performance monitoring
**performance monitoring
****install tools
***install tools
****check results
***check results
**re-tuning & hw recommendations
**re-tuning & hw recommendations
**application performance check
**application performance check
****monitor/processor -- python
***monitor/processor -- python
****reporting -- php  
***reporting -- php  
**full text for signatures
**full text for signatures
* Failover
* Failover
Line 42: Line 42:
* IT Admin
* IT Admin
**Monitoring -- plans
**Monitoring -- plans
****Implementation
***Implementation
**Backup & Redundancy plan
**Backup & Redundancy plan
****Implementation
***Implementation
* Capacity Planning
* Capacity Planning
**(see above) Archiving Discussion
**(see above) Archiving Discussion
****Implement archiving?
***Implement archiving?
****RRD?
***RRD?
**Data growth analysis
**Data growth analysis
**New feature planning
**New feature planning
Line 70: Line 70:
* Friday
* Friday
**Query analysis pt.2
**Query analysis pt.2
**Troubleshooting  
**Troubleshooting


= Travel Schedules =
= Travel Schedules =

Revision as of 00:44, 10 March 2009

Mission

Make the web better.

  • Harvest crash report data
  • Generate aggregate statistics on data to understand trends
  • Publish individual reports for drill-downs and forensics
  • Determine the cause and frequency of all major crashes
  • Help Mozilla focus development resources in areas of highest impact

Goals this Week

  • Understand why reporter queries time out
  • Evaluate partitioning strategy
  • Evaluate hardware configuration
  • Evaluate backup and replication methods
  • Develop better/best practices for PostgreSQL
  • Performance
    • pg.conf changes
    • fs/os changes
    • query tuning
      • monitor
      • reports
      • interactive query tuning
        • memory checks
    • index/schema check
    • performance monitoring
      • install tools
      • check results
    • re-tuning & hw recommendations
    • application performance check
      • monitor/processor -- python
      • reporting -- php
    • full text for signatures
  • Failover
    • Uptime requirements
    • Prepare failover plan
    • Failover config & scripts
  • Partitioning
    • Partition scheme check
    • Check for bad queries
    • Rolloff plans
    • Deal with archive partition
  • IT Admin
    • Monitoring -- plans
      • Implementation
    • Backup & Redundancy plan
      • Implementation
  • Capacity Planning
    • (see above) Archiving Discussion
      • Implement archiving?
      • RRD?
    • Data growth analysis
    • New feature planning
  • Tuesday
    • Partitioning
        • RRD/Archving?
    • Python Check
    • Full Text
    • Initial Replication
  • Wednesday
    • Continue replication
    • Query analysis etc.
    • Capacity planning data
    • Bug list and future feature planning
    • Interactive query checking
  • Thursday
    • Capacity Planning session
        • Schema changes?
    • PHP analysis?*
    • Deploy replication?
  • Friday
    • Query analysis pt.2
    • Troubleshooting

Travel Schedules

  • aking
    • Arrive SJ @ 10:30 - will miss first half of Monday's meetings
    • Depart SJ @ 17:10
    • Wild Palms
  • lars
    • Arrive SJ @ 17:00 Sunday, March 8
    • Depart SF @ 22:12 Saturday, March 14
    • Sweaty Palms
  • morgamic
    • Arrive SJ @ 22:30 Sunday, March 8
    • Depart SJ @ 19:20 Friday, March 13
    • Wild Palms