
--
You received this message because you are subscribed to a topic in the Google Groups "codename-taurus" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/codename-taurus/RuVP8k6-PPI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to codename-taur...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/codename-taurus/4cfe041b-7f10-43a9-9ac0-c5565c10e5fan%40googlegroups.com.

I don't think this is a code writing service, if you need to master Taurus the best option is attending free BlazeMeter University which provides The Complete Taurus CourseAs an exception I provide some inputs.It's possible to specify a Load Profile in Taurus which has throughput option allowing to control the number of requests per second which Taurus generates (if the underlying Executor supports it)For default Taurus executor which is JMeter the throughput is implemented via Throughput Shaping Timer which in its turn provides load_profile property allowing to specify the desired load pattern.So if you need to perform a spike as at your image the relevant load profile would be something like
const(500,10m) line(500,5000,1m) const(5000,5m) line(5000,500,1m) const(500,4m)The property can be propagated to the underlying JMeter engine as per JMeter Properties and Variables user manual sectionPutting everything together:---scenarios:example:requests:execution:concurrency: 5000hold-for: 20mthroughput: 500scenario: examplemodules:jmeter:properties:load_profile: const(500,10m) line(500,5000,1m) const(5000,5m) line(5000,500,1m) const(500,4m)If you run this YAML config file as bzt -gui you will see something like:
To view this discussion on the web visit https://groups.google.com/d/msgid/codename-taurus/3a81544c-9848-438a-9d8a-d621f4850b0dn%40googlegroups.com.
<Untitled.png>