Support concurrent executions of scenarios
See original GitHub issueCurrently it’s only possible to execute feature classes in parallel. In case you have independent scenarios (and you really should) it would be nice to run them concurrently. The current codebase does not support this. First of all the reporting is inherently sequential and there is some state in the Runtime class (skipNextStep
and scenarioResult
). I would be happily contributing a patch, but this would require a major change of some of the internal structure.
Issue Analytics
- State:
- Created 10 years ago
- Comments:37 (13 by maintainers)
Top Results From Across the Web
Configuring reserved concurrency - AWS Lambda
This topic details how to manage and configure reserved concurrency. If you want to decrease latency for your functions, use provisioned concurrency.
Read more >Function concurrency limits and throttling in AWS Lambda
AWS Lambda concurrency limits can result in throttles to your ... Lambda requires at least 100 unreserved concurrent executions per account.
Read more >Using Scenarios - Oracle Help Center
Concurrent execution of multiple instances of a scenario or load plan may be undesirable, particularly if the job involves writing data. You can...
Read more >The Everything Guide to Lambda Throttling, Reserved ...
Concurrent Executions — Processes that are are being executed by AWS Lambda Functions at the same time . Request — An event that...
Read more >Gatling: Concurrent execution within a scenario - Stack Overflow
You should have 1 single scenario with users performing request A, then request B, then requests C, D and E concurrently using resources....
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
If your tests are that slow you should fix your architecture.
https://skillsmatter.com/skillscasts/8567-testable-software-architecture
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.