Maximum number of schedule that can be executed per minute

Hello Team,

In my project, I have four workflows, each containing five activities. Each minute, four workflows are executed. However, I am experiencing many task timeout errors, and my activities have low execution rates.

Therefore, I would like to know the maximum number of schedule that can be executed per minute. Additionally, I have not found any error logs, but I have encountered some tasks that are either missing or have timed out.

1 Like

There is no limit on the number of activities that can be executed per minute, assuming that your cluster and workers are configured appropriately.

1 Like

Thank you for your reply.

Could you please advise on the appropriate configuration settings? Currently, I am using the default configuration.

At present, I am using a MySQL backend with one history service, one matching service, and one worker (Temporal worker).

How should I configure the system to enable full performance?

Hello team,

I am referencing the following posts to analyze my metrics:

  • 10758
  • 2263
  1. Persistence Latency:
    I am using MySQL as the backend, and I have noticed that the persistence latency is very slow, sometimes taking up to ten seconds. My MySQL setup is version 8.0, with 2 CPU cores and 6 GB of RAM, but the usage statistics show 36m CPU and 867 MiB memory.

  2. Sync Match:
    In my project, every minute, I have 4 workflows, and each workflow contains 5 activities.

  3. Workflow Lock Contention:

  4. Shard Lock Contention:

  5. Resource Exhaustion:

Imgur: The magic of the Internet

I believe the main issue is the persistence performance being too slow. However, it seems abnormal that MySQL resources are not fully utilized. Could you please advise on how I can further optimize Temporal’s performance?

Thank you.