-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ENH] In stress testing, there were some task have not been started. #5360
Comments
To address the issue of tasks not starting during high concurrency stress testing, it's important to understand the underlying architecture and configuration of Elsa Workflows. The issue may be related to the limitations of the workflow engine under heavy load or a configuration that does not support high concurrency. Elsa Workflows is designed to handle both short-running and long-running workflows, and it supports parallel execution of activities. However, there may be limitations based on the persistence provider used, the job scheduler configuration, and the resources available to the application. To troubleshoot and resolve this issue, consider the following steps:
Please note that without access to the specific configuration and setup of your Elsa instance, as well as detailed logs and system information, it's challenging to provide a precise solution. The steps above are general guidelines to help you investigate and address the issue. This comment was generated by Glime. |
maybe it was because immediately report task executed completed in webhook.
` |
In stress testing, there were some task have not been started.Poor support for high concurrency.
The text was updated successfully, but these errors were encountered: