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

"Initial Availability" and "Availability" #602

Open
JensMyrup opened this issue Feb 22, 2021 · 0 comments
Open

"Initial Availability" and "Availability" #602

JensMyrup opened this issue Feb 22, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@JensMyrup
Copy link

Whether running courses or larger events, the "availability" tends to be a memory eater. At this moment, a total of 51 labs are instantly available, thus eating up resources. The main reason for having a high availability is in the case of mass sign-ups during large events/classes where we expect many to sign up within a short duration of time. After this mass-signup phase the need for instantly available labs will be much smaller, but with the current setup we keep having all these labs available until the capacity limit is reached (often this is set as worst case, so it does not happen) or the event expires.

A more efficient approach would be that the specified "availability" is available only initially, but then drops to 2.

So if I choose an availability of 20, then 20 labs will be available initially, and after the first 18 signups there will always be 2 labs available for additional signups (until the maximum is reached).

@mrtrkmn mrtrkmn added the enhancement New feature or request label Apr 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants