Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce memcached and split the check-presets API #2546

Open
achimnol opened this issue Jul 24, 2024 · 0 comments
Open

Introduce memcached and split the check-presets API #2546

achimnol opened this issue Jul 24, 2024 · 0 comments
Labels
comp:manager Related to Manager component type:enhance Enhance component, behavior, internals without user-facing features urgency:5 It is imperative that action be taken right away.
Milestone

Comments

@achimnol
Copy link
Member

achimnol commented Jul 24, 2024

Currently, our frontend is heavily using the check-presets API in many places, including when polling the current system resource usage.

This API is very heavy in terms of database transactions because it locks sessions, agents, groups, keypairs tables as a single read-only transaction.

Let's split this API into two which internally uses the same query underneath:

  • check-presets: Just return the filtered resource preset list for the session creation UI. Infrequently invoked.
  • check-resources: Return the full resource usage information. Frequently invoked and should be heavily cached.
    • Add an option to bypass the cache, for cases when the client/frontend needs manual updates.

To achieve this, let's introduce memcached as a database caching backend with aiomcache.

This issue overrides #2366.

@achimnol achimnol added type:feature Add new features comp:manager Related to Manager component type:enhance Enhance component, behavior, internals without user-facing features urgency:5 It is imperative that action be taken right away. labels Jul 24, 2024
@achimnol achimnol added this to the 24.03 milestone Jul 24, 2024
@achimnol achimnol removed the type:feature Add new features label Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
comp:manager Related to Manager component type:enhance Enhance component, behavior, internals without user-facing features urgency:5 It is imperative that action be taken right away.
Projects
None yet
Development

No branches or pull requests

1 participant