Holiday Configuration: Increased Queue Limits and Reduced Cluster Capacity

Holiday Configuration: Increased Queue Limits and Reduced Cluster Capacity

Published: 22 Dec 2025 by NEMO Team

NEMO2 Holiday Configuration

To accommodate the holiday period, we are making temporary changes to NEMO2’s configuration, balancing increased flexibility for users with energy conservation efforts.

Increased Queue Limits

During the holidays, queue limits are significantly increased to give you more flexibility. You can now submit up to 10,000 jobs and request larger jobs with more CPU cores. This allows you to make better use of the available resources during the typically quieter holiday period.

The increased limits will be automatically lifted on January 7, 2026, when standard queue limits will be restored.

Reduced Cluster Capacity for Energy Savings

To conserve energy during the holidays, we will shut down a portion of the compute nodes. Sufficient capacity remains online to process jobs throughout the holiday period, but please expect potentially longer queue times due to the reduced number of available nodes.

Questions or Issues?

If you have questions about the holiday configuration or experience any issues, please submit a ticket.


The NEMO Team wishes you happy holidays and a happy New Year 2026!

NEMO2 Maintenance Queue Limits Energy Saving

Latest Posts

SSH Configuration Issue Fixed: Local Authorized Keys No Longer Working

An SSH configuration issue on the login nodes has been fixed. SSH keys stored in local authorized_keys files are no longer accepted. This behavior was never intended - please use SSH keys configured in login.bwidm.de instead.

Holiday Configuration: Increased Queue Limits and Reduced Cluster Capacity

Over the holiday period, we’re increasing queue limits to 10,000 jobs while reducing cluster capacity for energy savings. Normal operation resumes automatically on January 7, 2026.

NEMO2 Rolling Upgrade: Enhanced Security and Performance

NEMO2 has undergone a rolling upgrade with security, firmware/BIOS, and Slurm 25.05.5 updates. We planned and executed all steps to keep downtime for users as minimal as possible. Running jobs continued without interruption throughout the process.