You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PREvant allows us to instantiate individual environments very quickly. While this being a great feature, these easily created environments can easily be forgotten, thus causing an issue of draining and running out of resources at the hosting system.
To overcome this issue, an automatic cleanup for those unwanted environments is needed, so that if they're not being used, they can be deleted after a specific time period automatically. For this purpose, the creation time and last updated timestamp for each tile/environment can be kept in account. This data can be utilized to dynamically modify or prolong the configuration, ensuring tiles are deleted only when being idle and not being used for specific amount of time.
Please also consider to not restart the environments on a reboot. Esp for using Docker you have to wait ages at boot time, till all containers are running again.
I'm considering that this deletion should be more sophisticated once PREvant is able to collect metrics of the hardware utilization (see #201) so that things get cleaned up when the backend (K8s or Docker) hardware utilization reaches a certain threshold.
PREvant allows us to instantiate individual environments very quickly. While this being a great feature, these easily created environments can easily be forgotten, thus causing an issue of draining and running out of resources at the hosting system.
To overcome this issue, an automatic cleanup for those unwanted environments is needed, so that if they're not being used, they can be deleted after a specific time period automatically. For this purpose, the creation time and last updated timestamp for each tile/environment can be kept in account. This data can be utilized to dynamically modify or prolong the configuration, ensuring tiles are deleted only when being idle and not being used for specific amount of time.
Check crate chrono to address this issue.
The text was updated successfully, but these errors were encountered: