---------------------------------------------------------------------------------------------
IterationNumber User-ID Param_1                 Param_2
---------------------------------------------------------------------------------------------
1               1       Series_1_value_1                Series_2_value_1
2               1       Series_1_value_2                Series_2_value_2
3               1       Series_1_value_3                Series_2_value_3
4               1       Series_1_value_4                Series_2_value_4
5               1       Series_1_value_5                Series_2_value_5
1               2       Series_1_value_6                Series_2_value_6
2               2       Series_1_value_7                Series_2_value_7
3               2       Series_1_value_8                Series_2_value_8
4               2       Series_1_value_9                Series_2_value_9
5               2       Series_1_value_10       Series_2_value_10
1               3       Series_1_value_11       Series_2_value_11
2               3       Series_1_value_12       Series_2_value_12
3               3       Series_1_value_13       Series_2_value_13
4               3       Series_1_value_14       Series_2_value_14
5               3       Series_1_value_15       Series_2_value_15
1               4       Series_1_value_16       Series_2_value_16
2               4       Series_1_value_17       Series_2_value_17
3               4       Series_1_value_18       Series_2_value_18
4               4       Series_1_value_19       Series_2_value_19
5               4       Series_1_value_20       Series_2_value_20

Referring to the attachment, Block Size is FIVE ‘5’. Upon reaching and using
the last value within the BLOCK size, the THREAD will pick/use the VALUE
based on the configuration in settings for “Recycle on EOF?” or “Stop Thread
on EOF”. The concept of BLOCK size for User Parameter is there available in
LoadRunner and becomes very handy when users will have to use DATA
restricted to their specific credentials/pool (scenarios where form data
depends on the User Role and User-ID). It would be really worth if the
feature can be implemented in the JMeter CSV Data Config Element.

BLOCK SIZE PARAMETER HELP IN USING A SINGLE CSV FILE ACROSS MULTIPLE USERS
AND ALSO ENABLE EACH USERS TO USE THEIR OWN POOL/BLOCK OF DATA, EXAMLPE IF
BLOCK SIZE IS “5”
1st USER WILL USE 1st – 5 VALUES (Values in ROW 1-5)
2nd USER WILL USE NEXT 5 VALUES (Values in ROW 6-10)
3rd USER WILL USE NEXT 5 VALUES (Values in ROW 11-15)
4th USER WILL USE NEXT 5 VALUES (Values in ROW 16-20)
…
…


Regards,
Vineeth S

--
View this message in context: 
http://jmeter.512774.n5.nabble.com/Block-Size-Feature-in-CSV-Data-Config-tp5484937p5484937.html
Sent from the JMeter - User mailing list archive at Nabble.com.

Reply via email to