distributed-load-testing-on-aws icon indicating copy to clipboard operation
distributed-load-testing-on-aws copied to clipboard

Published 20 hours ago • verified publisher icon aws-solutions

Consider to increase the CONCURRENCY per container to simulate

Open yike5460 opened this issue 4 years ago • 1 comments

Our maximum CONCURRENCY value is 200, what's the reason result such limit? Can we increase to like 500 by adjust the Fargate allocated resource accordingly?

yike5460 avatar Jan 27 '21 02:01 yike5460

@yike5460 Thanks for your feedback.

There's no strong reason to limit the maximum concurrency to 200. If you want, you can change the limit on the source code. Meanwhile, we are validating what could be the reasonable maximum concurrency so that we can update the number in the next release.

beomseoklee avatar Feb 09 '21 22:02 beomseoklee

Concurrency limits were removed in v1.3.0. However, concurrency is limited by the CPU and memory in each AWS Fargate container, and the amount of cpu and memory used can vary based on each individual test being run. We provide guidelines on how to increase CPU and memory in the implementation guide.

G-Lenz avatar Nov 04 '22 14:11 G-Lenz