Groups
Groups
Sign in
Groups
Groups
codename-taurus
Conversations
Labels
About
Send feedback
Help
locust.io support
56 views
Skip to first unread message
Omar Moharrem
unread,
Apr 25, 2022, 5:15:08 PM
4/25/22
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to codename-taurus
When doing locust distributed testing i set my concurrency to 1000 and 2 workers. then i see blazemeter reporting 500 total concurrency.
I saw this in the code of locust executor and i was wondering if this is a bug
if self.is_master:
concurrency = math.ceil(concurrency / float(self.expected_workers))
https://github.com/Blazemeter/taurus/blob/82e44638ac80c5bd37765d36f0018e1f9899b80a/bzt/modules/_locustio.py#L86
is there a reason to divide the concurrency over the expected workers? i would expect 1000 concurrency and not less.
Reply all
Reply to author
Forward
0 new messages