Include per app invocation limits #39
Conversation
![mesa-dot-dev[bot]](https://avatars.githubusercontent.com/in/1050077?s=60&v=4){kind=small}
There was a problem hiding this comment.
Performed full review of 64aea20...32736b7
Tip
⚡ Quick Actions
This review was generated by Mesa.
Actions:
Slash Commands:
/review- Request a full code review/review latest- Review only changes since the last review/describe- Generate PR description. This will update the PR body or issue comment depending on your configuration/help- Get help with Mesa commands and configuration options
1 files reviewed | 1 comments | Review on Mesa | Edit Reviewer Settings
| | Concurrent browsers | 5 | 50 | Custom | | ||
| | Concurrent invocations | 5 | 50 | Custom | | ||
| | Persistent browsers | 5 | 50 | Custom | | ||
| | Concurrent invocations per app | 5 | 20 | Custom | |
There was a problem hiding this comment.
The limit for 'Concurrent invocations per app' is set to 20 for the Start-Up tier, while 'Concurrent invocations' (total) is set to 50. This creates a logical inconsistency - if the total concurrent invocations is 50, but per-app is limited to 20, it suggests users could have at least 3 apps running concurrently (20+20+10=50). However, this relationship and the reasoning behind these specific limits should be clarified in the documentation to avoid user confusion about how these limits interact.
…-per-app-concurrency-limit
Sayan-
deleted the
sayan/kernel-279-code-execution-app-scaling--per-app-concurrency-limit
branch
Description
Update concurrency docs!
TL;DR
Updated pricing documentation to include new per-app invocation concurrency limits.
Why we made these changes
To prevent a single, high-traffic application from consuming all system resources, we've introduced per-app concurrency limits. This change ensures system stability and fair resource allocation. This documentation update makes users aware of the new behavior.
What changed?
Description generated by Mesa. Update settings