Introduce memcached and split the check-presets API #2546
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
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:
To achieve this, let's introduce memcached as a database caching backend with aiomcache.
This issue overrides #2366.
The text was updated successfully, but these errors were encountered: