...
- leveldb - 737k resources before failure
- slightly faster than an untuned postgres
- postgres - never timed out, 3.7mil before network disconnect
- opportunity for tunning, was tested with stock install
- adding index on key would help
- opportunity for tunning, was tested with stock install
determine units of jmeter results
No Format * Label - The label of the sample. If "Include group name in label?" is selected, then the name of the thread group is added as a prefix. This allows identical labels from different thread groups to be collated separately if required. * Num Samples - The number of samples with the same label * Average - The average elapsed time of a set of results * Min - The lowest elapsed time for the samples with the same label * Max - The longest elapsed time for the samples with the same label * Std. Dev. - the Standard Deviation of the sample elapsed time * Error % - Percent of requests with errors * Throughput - the Throughput is measured in requests per second/minute/hour. The time unit is chosen so that the displayed rate is at least 1.0. When the throughput is saved to a CSV file, it is expressed in requests/second, i.e. 30.0 requests/minute is saved as 0.5. * Kb/sec - The throughput measured in Kilobytes per second * Avg. Bytes - average size of the sample response in bytes. (in JMeter 2.2 it wrongly showed the value in kB)
Madison
- Focused on resource consumption
- Ran for ~48 hours
- CPU settled down after initial warm-up
- Will use jmeter graphing component next
- Will retrieve the number of resources created
...