[discourse] [Self-hosted] recommended hardware specs? #4338
-
Originally posted by jeremy.allocate on Discourse Looked around today for some documentation on the minimum system specs required to run a Flipt instance that get various amounts of traffic and couldn’t find anything. Is there an article or other documentation out there somewhere about this? We were running on .25 vCPU and just bumped it after seeing some “deadline exceeded” messages, but wondering if this was just way too low to start. Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
There isn’t any official documentation or minimum hardware specs published for Flipt. The project takes a configuration-driven approach, so resource needs depend on your traffic and setup. Running on .25 vCPU is likely too low for most production use cases—“deadline exceeded” errors usually mean the server can’t keep up with requests, which points to CPU or database bottlenecks. For better performance, consider increasing vCPU and memory, especially if you expect moderate or higher traffic. Production best practices include tuning your database connection pool, enabling caching (in-memory or Redis), and disabling debug logging to reduce CPU load. Flipt is designed to scale horizontally with an external database and optional Redis cache, so you can add more instances as needed for reliability and throughput. More details on production tuning are available in the operations guide and deployment docs. If you share more about your expected traffic or usage patterns, I can help suggest a starting point for vCPU and memory. To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
There isn’t any official documentation or minimum hardware specs published for Flipt. The project takes a configuration-driven approach, so resource needs depend on your traffic and setup. Running on .25 vCPU is likely too low for most production use cases—“deadline exceeded” errors usually mean the server can’t keep up with requests, which points to CPU or database bottlenecks.
For better performance, consider increasing vCPU and memory, especially if you expect moderate or higher traffic. Production best practices include tuning your database connection pool, enabling caching (in-memory or Redis), and disabling debug logging to reduce CPU load. Flipt is designed to scale horizontally w…