Socorro/Pre-PHX Smoketest Schedule: Difference between revisions

Revision as of 22:22, 10 January 2011

What we are going to test and how in terms of load
- what:
  - crashes are collected without error
  - all submitted crashes are collected
  - at what point do collectors fall over?
    - start with 40 test nodes at 1k crashes each, versus one socorro collector
      - assuming/hoping this will overwhelm one collector
      - back down nodes/crashes until we find a stable place
      - check ganglia to see where our bottlenecks are
- how:
  - ~~grinder (bug 619815) + 20 VMs (bug 619814)~~
  - Lars added stats and iteration to submitter.py for initial smoke-test bug 622311
  - 40 seamicro nodes standing by to test, using socorro-loadtest.sh
- when:
  - waiting on deps in tracking bug 619811
  - tentative start date - Monday Jan 10 2010
    - minimum 2-3 days testing; as much as we can get
what component failure tests we will run
- disable individual components to see test failure/recovery
  - hbase
  - postgresql
  - monitor
  - processor
  - others?
Outstanding issues
- how many crashes to use?
  - pool of 500 random real-world crashes?

@@ Line 6: / Line 6: @@
 *** all submitted crashes are collected
 *** at what point do collectors fall over?
+**** start with 40 test nodes at 1k crashes each, versus one socorro collector
+***** assuming/hoping this will overwhelm one collector
+***** back down nodes/crashes until we find a stable place
+***** check ganglia to see where our bottlenecks are
 ** how:
 *** <strike>grinder ({{bug|619815}}) + 20 VMs ({{bug|619814}})</strike>