Hi, everyone! I have a question regarding performance of database operations: • Is every log entry stored on the database? • Is every task execution registered on the database? • Is there any built-in automatic history clean-up of old data? • Wouldn't it be better to use redis to avoid high frequency operations and thus high IO on the database? My concern is that if I proceed to break my flows in as many tasks as it might make sense I might cause a performance bottleneck on the DB, which seems counterproductive. Ideally (and it might not be possivle), I should be able to break any flow in as many tasks as I want without this decision affecting performance

Hey @Luis Henrique, are you asking because you’re on server?

I'm asking because I plan on running prefect server on my own cloud, yes. I'm sorry if that wasn't what you asked, I'm still getting familiar with prefect terms

Ah yeah no worries, just needed more context. There’s a #C014Z8DPDSR, channel but it doesn’t really matter. I’ll answer the questions. • Yes all logs are stored • Yes all tasks are registered • No to cleanup, you’d have to truncate tables • If you have to use Redis, you’re likely using server at a scale that makes it harder to manage. You can use Redis, but this is not something we would provide help more. Cloud is designed to handle these as our managed offering. Each task hits the API when it updates state. There are at least 3 calls for each task run.