load/notes.txt

@@ -5,7 +5,16 @@ Goals
     Find out what categories of users can fit into which sized hardware
         i.e. a small shop with 10 users can infinitely use the tiniest droplet??
     Does database size matter when it comes to load? (not specifically reporting on huge numbers of records for example, just normal sane operation)
-        
+
+
+Load / capacity / stress testing			
+    Find problem areas - dev / pre-release
+    Have an idea what hardware can support what load of users - marketing/ support / sales
+    how far can it go before failure?
+    what is the maxium simultaneous users for a given hardware config
+        digital ocean can help with this as we can spin up progressively more peformant droplets and load / stress test them to know		
+    Does it recover from failure?
+    Find prior unknown bugs that result in failure under stress      
 
 todo: make sure it's simulating realistically, i.e. how users would really work with it as much as possible    
 todo: add parameters for max of each object or read data and auto know, create objects, generate report,filterid