Hi Sergio, Sorry forgot to say that that isn't a good option for me. I thought about it but I dynamically build remote agents off a standard build image and that makes my start procedure immensely difficult as I'd need to split the files and copy them to the clients before the test. I also don't have a standard number of clients so the splits are different. If I do that I could also just re-randomize my files too.
Cheers Oliver On 7 November 2013 11:28, Sergio Boso <[email protected]> wrote: > Il 06/11/2013 23.20, Oliver Erlewein ha scritto: > > Hi all, >> >> I'm sure that this is a common problem for those using JMeter executions >> across several machines. Can't really find any solution to this. So here >> goes: >> >> I have a plan that looks something like this: >> >> Test Plan >> |-- Thread Group >> |--CSV Dataset >> |--HTTP Sampler (login) >> |--.... >> >> If I remotely distribute this all remotes will 1st start with line one of >> the CSV file. In my case this will cause locking in the application, >> thereby destroying the test. Ideally I'd like to give the CSV file a >> random >> offset for each remote client, so that it would start iterating at various >> points in the CSV. This is not quite safe but should give me enough >> variance so that the chance of locking would be minimal. >> > The only way I have found to cope with this is to manually split the CSV > file, and copy each of these parts to each remote system, so that each > system uses its own set of lines. > > I'm looking forward to see if there is a better system > regards > > Sergio > > -- > > Ing. Sergio Boso > > > >
