arrivalRate lower than 1
See original GitHub issueideally it would be nice to have the ability to make request over a given duration with fewer concurrent virtual users than 1 per second. it looks like it is not possibile to specify an arrivalRate
lower than 1
.
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
arrivalRate lower than 1 using Artillery - load testing
I am trying to design load tests using Artillery on a computation-heavy API which typically requires at least a few seconds to send...
Read more >Test Scripts - Artillery.io
The above load phase is equivalent to the following: phases: - arrivalRate: 0 duration: 1.96 - arrivalRate: 1 duration: 1.96 - arrivalRate: 2...
Read more >arrival rate λ - an overview | ScienceDirect Topics
Whenever there is more than one customer at the checkout, however, a “bagger” is added, increasing the service rate to β per hour....
Read more >PFA_SMF_ARRIVAL_RATE - IBM
PFA performs this type of comparison to determine if the SMF arrival rate is higher than expected or lower than expected.
Read more >Little's law - Wikipedia
In mathematical queueing theory, Little's result, theorem, lemma, law, or formula is a ... long-term average effective arrival rate λ multiplied by the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
we are currently trying to load-test our cluster with artillery and it works pretty well though in our case single services take long running tasks and we need to stress both the cluster and individual service for given phases and scenarios.
@hassy the problem can indeed be solved by tweaking both
arrivalCount
andduration
properties each time and this is what we currently do though it feels quite strange at least to me doing the math each time again when trying to adjust the suite’s throughput better expressed with anarrivalRate
property. we’ve tried the previous patch #280 on our suites and the behaviour seems stable. just to make an example anarrivalRate
of.5
would represent one request each2
seconds and this once over a consistentduration
.What’s your use-case @ivoputzer? Can it be solved by using
arrivalCount
? AnarrivalRate
of less than 1 doesn’t really make sense intuitively.