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

12th bwHPC Symposium

The 12th bwHPC Symposium will take place on September 24th, 2026 and will be hosted by the University of Konstanz. Registration and call for abstracts are now open.

MathWorks Products: No General License Available on NEMO2

The statewide academic license agreement for MathWorks products at Baden-Württemberg universities expires on March 31, 2026. There will be no general MathWorks license available on NEMO2 specifically. Universities and other clusters may handle this differently. Please consider using open-source alternatives or contact us if you hold your own license.

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.