Update the tool's measuring methodology in the documentation.

We need a way to check whether a profile produces errors during benchmark steps or not.

• Create a benchmark config for 1M contents
• Run the downloader profile benchmark
• Run the R/W scenario benchmark
• Deliver benchmark insights

Create a benchmark process for a pre-installed Sensenet system
The benchmark should be repeatable - with 10000 contents for now.

• Create file structure
• Create sites for the 10k content structure
• Create sites for the 100k content structure
• Run a benchmark that uses different files to download
• Determine the import time for every database

The output format should be xls in this iteration.

We need a documentation for everyone to understand the concepts of the benchmark

WARNING: Do not write detailed documentation about MSMQ configuration.

It consists of:

• DB installation workflow
• The benchmark measurement workflow
• The upgraded documentation of the benchmark tool

@kavics would like to have a script that automagically "solos" the benchmark web environment received in a parameter

• Every sensenet web "node" switches off in the benchmark environment
• The requested web "node" gets activated

• Define what counts as a small, medium or big file
• Decide the method of the measurement
• Measure

There should be a scenario when we benchmark as a profile writes in the db while another one is downloading simultaneously.

• Create a writer profile
• The reader profile runs a content query as well
• Run the benchmark with an increasing number of simultaneous writer and reader profiles
• At the end of the benchmark process, we restore the db (ie delete the folder where the profiles uploaded)

1- Develop a measurement unit that indicates the momentary performance value (served requests/sec) and able to detect the performance maximum.
2- Develop a load control unit that able to hold the performance on the specified value (e.g. 70%) for unlimited time even near the maximum value (e.g. 95%).