Hi guys, Not to minimize the suggestion for improvement, but the quick workaround is to create the CSV with 5 values (or 5 sets of values) per row so each v-user can use a block of values.
A second workaround, if you actually want to change the block size often, is to keep your test data in a database. With a simple MySql setup, you can easily use the table index to create the scenario you were talking about. The database scenario gives a lot more flexibility than with CSV in other more complex scenarios as well (for example what if you need to have dynamic block sizes). --Adrian S On Mon, Feb 20, 2012 at 1:02 PM, Oliver Lloyd <[email protected]>wrote: > One of the advantages of JMeter over LoadRunner is the fact it is > lightweight > and not encumbered by excessive features that - whilst making things appear > easier - actually end up restricting what you can do. > > So sure, LR can do what you say but that is because it pre-processes the > data file before the test is started, bundling up each little thread with > it's own data and instructions on what to do with it. It's a bit like > sending your kids off to school with a packed lunch. JMeter does not really > do this, certainly not over multiple hosts; you have to make the packed > lunch for your kids yourself (ie. you have to pre-process the data > yourself). > > > ----- > http://www.http503.com/ > -- > View this message in context: > http://jmeter.512774.n5.nabble.com/Block-Size-in-CSV-Data-Config-tp5498518p5498699.html > Sent from the JMeter - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
