I'd also recommend using a centralised store like redis -- this is the direction we went to solve the problem of sharing test data amongst N nodes in a grid (of jmeter machines) https://flood.io/blog/9-sharing-test-data
Then if you don't want the hassle of using a redis data set plugin, you can optionally stick something like webdis in front of the redis box which means your data is accessible via simple http calls (with a regex extractor or the like) https://github.com/nicolasff/webdis Regards, Tim Koopmans +61 3 9221 6309 [image: Flood IO Pty Ltd] <https://flood.io> Level 27, 101 Collins Street Melbourne, Vic 3000 On Fri, Oct 31, 2014 at 5:50 AM, Flavio Cysne <[email protected]> wrote: > I'll just link you to a third party comparison, since I never used Visual > Studio Load Test tool. > > > http://sqa.stackexchange.com/questions/9572/comparison-of-jmeter-vs-visual-studio-load-test > > Since JMeter don't have any built-in test data distribution component is up > to you to decide what is the best approach for spreading your test data. > You could use Maven and JMeter Maven Plugin or JMeter Ant Task. The > goals/tasks with the distribution strategy could be defined in the pom.xml. > Since you can pass parameters to maven execution, the number of machines > you'll have to distribute your test data can be configurable. > > Any way, as JMeter is an open-source project and allows plugins to be > attached to it, you can also write your own test data distribution plugin. > > JMeter-Plugins <http://jmeter-plugins.org> has also a plugin, Redis Data > Set > <http://jmeter-plugins.org/wiki/RedisDataSet/>, that can help you with > this. >
