Auto-hibernation and scheduling: save resources with smart start/stop

Auto-hibernation and scheduling: save resources with smart start/stop

Keeping your server available without wasting resources is a balancing act. HostChicken includes auto-hibernation and flexible scheduling so your world sleeps when no one’s around and wakes up right on time. This guide explains how these features work and how to set them up for a smooth, always‑ready experience.

What is hibernation?

Hibernation pauses your server when it’s idle. The world is saved, CPU/RAM usage drops, and billing (where applicable) can be reduced. When someone tries to connect—or you press Start—the server wakes and players can join.

Benefits:

• Lower costs / resource usage

• Less wear on infrastructure

• Environmentally friendly

How wake-on-connect works

When a player connects to your server address while it’s hibernating, HostChicken intercepts the handshake and boots the server automatically. The first join may take 30–60 seconds during world load, then it’s normal gameplay.

Cold vs warm boots:

• Warm boot: The server recently ran; startup is faster, caches are hotter.

• Cold boot: The server has been idle a while; startup may take longer while chunks and data are reloaded.

Enable auto-hibernation

1. Open your server settings in HostChicken.

2. Enable Auto-Hibernate.

3. Set idle timeout (e.g., 10–20 minutes after last player leaves).

4. Keep Wake on Player Connect enabled for a seamless experience.

Add a simple schedule

If your group plays during certain hours, scheduling can pre-warm the server:

1. Go to Scheduling.

2. Add Start events before your peak times (e.g., weekdays at 4:00 PM).

3. Add Stop events after bedtime (e.g., 11:30 PM).

4. Keep wake-on-connect on for weekends or surprise sessions.

Pre‑warming for events

Hosting an event or boss fight? Pre‑warm the server:

• Schedule a start 10–15 minutes before the event.

• Jump in, fly around spawn to load chunks, and run a quick `/timings` check if you use Paper.

• Announce the address so everyone connects smoothly.

Best practices

• Combine schedules with auto-hibernate: Start before sessions, then let idle timeout handle the rest.

• Announce scheduled restarts: A quick message keeps everyone happy.

• Use smaller view/simulation distances if frequent wake-ups are slow.

• Take a backup before long sleeps following major changes.

Pro tip for modpacks:

• Some heavy modded servers benefit from slightly longer idle timeouts so they don’t bounce up and down between hibernation during short breaks.

Observability: know when to hibernate

• Watch average player session length. If people take short breaks, use a longer idle timeout.

• Track CPU/RAM during peak hours. If memory bloat occurs over time, scheduled restarts can help.

• If TPS drops after long uptime, a nightly restart plus hibernation can stabilize performance.

Troubleshooting

• “Players time out on first join”: Increase idle timeout a bit or pre-warm during busy windows.

• “Server never sleeps”: Check for chunk loaders or bots keeping it active.

• “Wakes too often”: Raise idle timeout or adjust wake-on-connect settings.

If you suspect a plugin or mod is preventing idle detection, temporarily disable it and test. Chunk loaders, ticking tile entities, or bots can trick the server into thinking it’s active.

Example schedules

• School-year schedule

• Start: 4:00 PM Mon–Fri

• Stop: 10:30 PM Mon–Fri

• Wake on connect: Enabled (always)

• Weekend flexible play

• No scheduled start

• Auto-hibernate after 15 minutes idle

• Wake on connect: Enabled

Why this matters

Good scheduling makes your server feel “always ready” without being “always running.” You’ll spend less, waste less, and still be able to play whenever inspiration strikes.

FAQ

• Does hibernation delete my world?

• No. The world is saved to disk first. Hibernation is a pause, not a wipe.

• Can friends wake the server without me?

• Yes, if wake-on-connect is enabled. Share the address and they can join anytime.

• Will scheduled stops kick players?

• A stop is a restart/stop event—warn players a few minutes before via your server MOTD or a broadcast.

• Do I need SRV records for wake-on-connect?

• No. DNS is separate from hibernation. Use SRV only for non‑default ports or specific hostnames.