Currently, GOrimpo runs exceptionally well for days on the VPS. However, to maintain optimal long-term performance, clear potential memory fragmentation, and cleanly drop zombie connections or persistent API blocks we need an "Application Hygiene" routine.
Implement a self-terminating mechanism where the Go application cleanly exits (os.Exit(0)) under specific conditions. Since the application runs in a container, the Docker engine (restart: always or unless-stopped) will immediately spin up a fresh instance in milliseconds.
We need two new triggers controlled via config.yaml:
- Scheduled Hygiene: A time-based forced restart (e.g., every 24 hours).
- Reactive Hygiene: A forced restart triggered after a sequence of consecutive Circuit Breaker trips (e.g., 3 consecutive trips).
Currently, GOrimpo runs exceptionally well for days on the VPS. However, to maintain optimal long-term performance, clear potential memory fragmentation, and cleanly drop zombie connections or persistent API blocks we need an "Application Hygiene" routine.
Implement a self-terminating mechanism where the Go application cleanly exits (
os.Exit(0)) under specific conditions. Since the application runs in a container, the Docker engine (restart: alwaysorunless-stopped) will immediately spin up a fresh instance in milliseconds.We need two new triggers controlled via
config.yaml: