#2533
  • Created on
    2012-09-20 19:13
  • Reported by
    drewhk
  • Status
    New
  • Priority
    High (2)
  • Assigned to
    -
  • Milestone
    Rollins
  • Plan Level
    Subtask
  • Due Date
    -

Attachments

Related Tickets

Think about long running performance and stability tests

To improve stability we should get more insight of the long-term behavior of Akka.

- How long can we afford to run tests?
- Do we want to run these tests for different versions, or the latest, or latest released? Periodic snapshots of master? (two-week, or such)
- Ideal would be tests that run "infinitely long", and have weekly automatic reports (some leaks might materialize as a very slow drift of memory usage so they don't result in crashes).
- Also, a realistic and sufficiently complex system is needed -- a simple ping-pong might not do the trick.
- A good opportunity to dogfood Atmos

Let's Discuss!
User picture
  on 2012-10-23 15:31 *
By viktorklang
Milestone changed from Performance to Coltrane
User picture
  on 2012-11-01 12:24 *
By viktorklang
Priority changed from Normal (3) to High (2)
User picture
  on 2012-12-05 16:11 *
By rkuhn
Estimate changed from Large to Medium
Sum of child estimates changed from 7.0 to 3.0
User picture
  on 2012-12-17 08:34 *
By Patrik Nordwall
Assigned to set to login
What more thinking is needed here? Can we create more concrete tickets if something is not covered by existing tickets?
User picture
  on 2012-12-18 09:03 *
By rkuhn
Moving to later, since we’ll start with the cluster stress test of #2786 and see how that goes. What that does not cover is how to run the test (for which branches/JVMs/OS).
User picture
  on 2012-12-18 09:03 *
By rkuhn
Milestone changed from Current to Coltrane
User picture
  on 2013-05-16 14:13 *
By rkuhn
Milestone changed from Coltrane to Rollins