Originally created by @spammenotinoz on GitHub (Aug 26, 2025).
Check Existing Issues
I have searched the existing issues and discussions.
Problem Description
Currently the system is hit quite hard when a user first logs in.
This can be mitigated to some extent by reverse proxy caching (especially API endpoint)
The key cause is the model and permissions enumeration relating to workspace models.
With a fast database this isn't an issue, however for many users this experience is far from optimal.
Desired Solution you'd like
Break-out Workspace\Models or somehow LazyLoad in the background, as to not impact the login experience.
Alternatives Considered
Disabling workspace models entirely.
Reverse Proxy Caching (fixes the page reload experience, but not logins after the cache has expired)
Additional Database Indexes (minor improvement)
Additional Context
No response
Originally created by @spammenotinoz on GitHub (Aug 26, 2025).
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
Currently the system is hit quite hard when a user first logs in.
This can be mitigated to some extent by reverse proxy caching (especially API endpoint)
The key cause is the model and permissions enumeration relating to workspace models.
With a fast database this isn't an issue, however for many users this experience is far from optimal.
### Desired Solution you'd like
Break-out Workspace\Models or somehow LazyLoad in the background, as to not impact the login experience.
### Alternatives Considered
Disabling workspace models entirely.
Reverse Proxy Caching (fixes the page reload experience, but not logins after the cache has expired)
Additional Database Indexes (minor improvement)
### Additional Context
_No response_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @spammenotinoz on GitHub (Aug 26, 2025).
Check Existing Issues
Problem Description
Currently the system is hit quite hard when a user first logs in.
This can be mitigated to some extent by reverse proxy caching (especially API endpoint)
The key cause is the model and permissions enumeration relating to workspace models.
With a fast database this isn't an issue, however for many users this experience is far from optimal.
Desired Solution you'd like
Break-out Workspace\Models or somehow LazyLoad in the background, as to not impact the login experience.
Alternatives Considered
Disabling workspace models entirely.
Reverse Proxy Caching (fixes the page reload experience, but not logins after the cache has expired)
Additional Database Indexes (minor improvement)
Additional Context
No response