Without getting to the techi aspect, sounds good, it's about time to have centralized datasets, so +1.
Does your implementation also allow to choose sharing mode between the load generators? I.e. if I want a single value to be used only once during a test, will your implementation support it, without this value being used more than once across the load generators? Shmuel Krakower. www.Beatsoo.org - re-use your jmeter scripts for application performance monitoring from worldwide locations for free. On Sat, Oct 26, 2013 at 10:23 PM, Philippe Mouawad < philippe.moua...@gmail.com> wrote: > Hello, > These days Cloud based testing is becoming popular and having to distribute > test data accross many servers through CSV can become painful if not > impossible. > Even without Cloud, when using distributed testing you always have to > replicate your data on all servers, which is a painful manual step. > > Shouldn't we introduce a new DataSet more suitable for these use cases ? > > We could do it in many different ways: > - Integrate an automatic CSV replicator, this would remain simple and would > not introduce any tier, but with cloud based it would not horizontally > scale easily > - Use a JDBC DataSet, but we would need to ensure it performs fine, and > jdbc protocol is not well suited for cloud based deployment (But it could > also be an interesting feature for Continuous Integration) > - Use a NOSQL repository (Redis seems to me the best choice) , see this > high level summary which I find interesting > > http://www.journaldunet.com/developpeur/outils/comparatif-des-bases-nosql/comparatif-des-bases-nosql-tableau-de-synthese.shtml > > I have implemented a new Redis (based on Java library for Redis) DataSet > which I plan to commit if no objection. > > It will introduce 2 new dependencies with Apache License: > - Jedis (http://code.google.com/p/jedis/) > - commons-pool > > Thoughts ? > -- > Regards. > Philippe M. > @philmdot <https://twitter.com/philmdot> >
