From 7f877082ff22de13640aa9f8ec0ab53592c1facf Mon Sep 17 00:00:00 2001 From: Maria Ines Parnisari Date: Mon, 6 May 2024 15:16:49 -0700 Subject: [PATCH] address feedback --- docs/content/getting-started/production-best-practices.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/getting-started/production-best-practices.mdx b/docs/content/getting-started/production-best-practices.mdx index b7b911a10..2983e692f 100644 --- a/docs/content/getting-started/production-best-practices.mdx +++ b/docs/content/getting-started/production-best-practices.mdx @@ -28,10 +28,10 @@ The following list outlines best practices for running OpenFGA in a production e We recommend: -1. Turn on caching via the flag `--check-query-cache-enabled`. This will reduce latency of requests, but it will increase the staleness of OpenFGA's responses. +1. Turn on caching via the flag `--check-query-cache-enabled`. This will reduce latency of requests, but it will increase the staleness of OpenFGA's responses. (The TTL is configurable). 2. Prefer having a small pool of servers with high capacity (memory and CPU cores) instead of a big pool of servers, to increase cache hit ratios and simplify pool management. 3. Turn on metrics collection via the flags `--metrics-enabled` and `--datastore-metrics-enabled`. This will allow you to debug issues. -4. Turn on tracing via the flag `--trace-enabled`, but set sampling ratio to a low value, for example `--trace-sample-ratio=0.3`. This will allow you to debug issues without overwhelming the tracing server. +4. Turn on tracing via the flag `--trace-enabled`, but set sampling ratio to a low value, for example `--trace-sample-ratio=0.3`. This will allow you to debug issues without overwhelming the tracing server. However, keep in mind that enabling tracing comes with a slight performance cost. ## Database Recommendations