yes CSV is faster - however you can do the same with a startup threadgroup instead of your test Beanshell can do almost anything java can do (and you write most of it within a java class so that you only call out to your java code (or you can write your own custom function in java)
regards deepak On Fri, Sep 30, 2011 at 2:02 PM, E S <electric.or.sh...@gmail.com> wrote: > Thanks for the help. The __time() function is exactly what I wanted. > Unfortunately, for the other value (the calculated one), I need access > to cryptographic libraries. It looks like I could use either > javascript or beanshell as long as they support importing third party > libraries, but frankly I think it's just too much work to figure out > at this point. I think I'll stick with the CSV Data Set Config element > for now. It'll probably be faster than interpreting javascript or Java > on the fly anyway. > > On Thu, Sep 29, 2011 at 6:55 PM, Deepak Shetty <shet...@gmail.com> wrote: > > you have __time function and javascript/beanshell in which you can write > > code to calculate values in. You can store these as variables or > properties > > for all the urls to use. > > > > regards > > deepak > > > > On Thu, Sep 29, 2011 at 4:50 PM, E S <electric.or.sh...@gmail.com> > wrote: > > > >> I have to include two query string parameters in my URLs. One of them > >> is a timestamp and the other is a calculated value based on the > >> timestamp. All the URLs can use the same two values. The tricky part > >> is that the server is validating both of these values and the > >> timestamp must be fairly up to date (within 30 minutes) or the server > >> will reject the request. > >> > >> Currently, I am achieving this by writing a Python script that will > >> get a the current timestamp, calculate the second value, and and > >> output both of them to a one line CSV file, which JMeter will read in > >> using a CSV Data Set Config element. > >> > >> This works fine except I have to re-create the CSV file every 30 > >> minutes or the timestamp gets stale. I think I know the answer to > >> this, but is there any other way to solve this that doesn't require me > >> to keep an up to date CSV file laying around? > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > >> For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > >> > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > >
