From 3262cd1a613e81fb1000d2254d6c920eace3a038 Mon Sep 17 00:00:00 2001 From: Ishaan Jaff Date: Wed, 4 Dec 2024 09:36:49 -0800 Subject: [PATCH] docs add FAq to life of a request --- docs/my-website/docs/proxy/architecture.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/my-website/docs/proxy/architecture.md b/docs/my-website/docs/proxy/architecture.md index eb4f1ec8de7..4cd23adb5e4 100644 --- a/docs/my-website/docs/proxy/architecture.md +++ b/docs/my-website/docs/proxy/architecture.md @@ -37,3 +37,10 @@ import TabItem from '@theme/TabItem'; - User Rate Limit - Team Limit - The `_PROXY_track_cost_callback` updates spend / usage in the LiteLLM database. [Here is everything tracked in the DB per request](https://github.com/BerriAI/litellm/blob/ba41a72f92a9abf1d659a87ec880e8e319f87481/schema.prisma#L172) + +## Frequently Asked Questions + +1. Is a db transaction tied to the lifecycle of request? + - No, a db transaction is not tied to the lifecycle of a request. + - The check if a virtual key is valid relies on a DB read if it's not in cache. + - All other DB transactions are async in background tasks \ No newline at end of file