We are trying to set-up temporal with a MySQL instance which has the database that our application uses that holds customer data.
In the same instance, we have created a separate DB for temporal and temporal_visiblity. We have disabled elastic search when we installed temporal.
Load: Currently we will have very few workflows but in the future we can have 100Ks of workflow a day that can run upto 20 minutes each.
In this setup,
- is there a config like SQL timeout in temporal that can prevent slow queries so that temporal workflows need not fight for DB CPU/memory with our critical production applications?
- Or is the only way to prevent this from happening is by have a low retention period in all namespaces, so that temporal and visibility DBs will have less data so that queries will be fast.
- In #2, I am assuming that if the retention is set to, say, 7 days, temporal will automatically delete the completed workflows after 7 days without manual intervention. Please correct me if I am wrong