Collect important stress profiles for regression analysis done by jenkins

We have a weekly job setup on CassCI to run a performance benchmark against the dev branches as well as the last stable releases.

Here's an example:

http://cstar.datastax.com/tests/id/8223fe2e-8585-11e4-b0bf-42010af0688f

This test is currently pretty basic, it's running on three nodes, with a the default stress profile. We should crowdsource a collection of stress profiles to run, and then once we have many of these tests running we can collect them all into a weekly email.

Ideas:

• Timeseries (Can this be done with stress? not sure)
• compact storage
• compression off
• ...