You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reasonix currently shares all user sessions, memory, task and API request resources globally without user_id isolation. When serving multiple end-users under one DeepSeek account, it will cause cross-user KV cache interference, scheduling conflicts and inaccurate rate limiting. We need to support configurable user_id to implement DeepSeek official multi-user isolation capabilities.
Why We Need This
DeepSeek API supports user_id isolation, including KV Cache isolation, scheduling isolation and content safety isolation
Without user_id isolation, different end-users’ reasoning contexts may conflict or leak with each other
Lack of user-level independent concurrency rate limit, causing 429 inaccurate triggering in multi-user scenarios
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Overview
Reasonix currently shares all user sessions, memory, task and API request resources globally without user_id isolation. When serving multiple end-users under one DeepSeek account, it will cause cross-user KV cache interference, scheduling conflicts and inaccurate rate limiting. We need to support configurable user_id to implement DeepSeek official multi-user isolation capabilities.
Why We Need This
Expected Features
https://api-docs.deepseek.com/quick_start/rate_limit
Beta Was this translation helpful? Give feedback.
All reactions