Hydra will remain powered up for use during the government shutdown.
The data center will have essential personnel through the shutdown
to maintain the integrity of the IT infrastructure.
Access to Hydra will not be cut off, so users will be able to submit jobs.
Any major failure of the IT infrastructure (hardware or software) is unlikely
to be fixed during the shutdown, hence accessibility to Hydra and its resources
cannot be guaranteed.
Support for Hydra will be limited to urgent matters
please contact SI-HPC-Admin@si.edu during the shutdown.
Hydra has been successfully moved to the new data center and is operational.
Updates are described in detail at the
HPC Wiki 2025 Data Center Move page.
Please take the time needed to read these pages before contacting us for support.
You can view the list of all the available modules:
as an HTML document, or
a plain ASCII text file.
You can also check the bandwidth between
SAO and HDC.
You can select to have this page refreshed every 5m,
20m, or
1hr, this one will auto-refresh every
20m.
Usage
Current snapshot sorted by nodes'
.
Usage vs time, for length=
and user=
highlighted.
As of Sat Oct 18 07:57:03 2025: #CPUs/nodes 5484/74, 0 down. Loads:
head node: 2.21, login nodes: 1.11, 0.63, 0.22, 0.18; NSDs: 3.21, 2.30, 1.43, 2.44, 2.97; licenses: none used.
Queues status: 36 disabled, none need attention, none in error state.
12 users with running jobs (slots/jobs):
Current load: 299.8, #running (slots/jobs): 422/40, usage: 7.7%, efficiency: 71.0%
no job in any of the queues.
52 users have/had running or queued jobs over the past 7 days, 68 over the past 15 days.
110 over the past 30 days.
Click on the tabs to view each section, on the plots to view larger versions.
You can view the current cluster snapshot sorted by name, no. cpu, usage, load
or memory, and
view the past load for 7, or 15, or 30 days as well as highlight a given user by
selecting the corresponding options in the drop down menus.
{}
This page was last updated on Saturday, 18-Oct-2025 08:02:00 EDT
with mk-webpage.pl ver. 7.3/1 (Oct 2025/SGK) in 0:50.
Warnings
Oversubscribed Jobs
As of Sat Oct 18 07:57:04 EDT 2025 (1 oversubscribed job)
Total running (PEs/jobs) = 422/40, 0 queued (job), showing only oversubscribed jobs (cpu% > 133% & age > 1h) for all users.
jobID name user age nPEs cpu% queue node taskID
10338386 casapipeline jmichail +1:09 1 685.4% uThM.q 65-14
⇒ Equivalent to 5.9 overused CPUs: 1 CPUs used at 685.4% on average.
Inefficient Jobs
As of Sat Oct 18 07:57:04 EDT 2025 (5 inefficient jobs, showing no more than 3 per user)
Total running (PEs/jobs) = 421/39, 0 queued (job), showing only inefficient jobs (cpu% < 33% & age > 1h) for all users.
jobID name user age nPEs cpu% queue node taskID
10397765 IQ_50p_iqtree morrisseyd 20:22 64 30.2% lThC.q 65-07
10397777 IQ_75p_iqtree morrisseyd 20:22 64 28.1% lThC.q 76-06
10261906 spades_1 santossam +7:20 20 7.9% mThM.q 65-12
10401563 Clusterf zhangy 18:31 16 16.0% lThC.q 65-05
10253677 Delphinidae_IQT mcgowenm +10:15 12 8.3% lThM.q 84-01
⇒ Equivalent to 133.6 underused CPUs: 176 CPUs used at 24.1% on average.
Nodes with Excess Load
As of Sat Oct 18 07:57:05 EDT 2025 (1 node has a high load, offset=1.5)
#slots excess
node #CPUs used load load
-----------------------------------
65-14 64 1 3.7 2.7 *Total excess load = 2.7
quota rule resource=value/limit %used
------------------- ------------------------------- ------
blast2GO/1 slots=12/110 10.9% for *
total_slots/1 slots=427/5960 7.2% for *
total_mem_res/2 mem_res=1.241T/35.78T 3.5% for * in queue uThM.q
total_mem_res/1 mem_res=662.0G/39.94T 1.6% for * in queue uThC.q
Memory Usage
Reserved Memory, All High-Memory Queues
Select length:
Current Memory Quota Usage
As of Sat Oct 18 07:57:05 EDT 2025
quota rule resource=value/limit %used filter
---------------------------------------------------------------------------------------------------
total_mem_res/1 mem_res=660.0G/39.94T 1.6% for * in queue uThC.q
total_mem_res/2 mem_res=1.241T/35.78T 3.5% for * in queue uThM.q
Current Memory Usage by Compute Node, High Memory Nodes Only
Limit slots for all users together
users * to slots=5960
users * queues sThC.q,lThC.q,mThC.q,uThC.q to slots=5176
users * queues sThM.q,mThM.q,lThM.q,uThM.q to slots=4680
users * queues uTxlM.rq to slots=536
users * queues sTgpu.q,mTgpu.q,lTgpu.q to slots=104
Limit slots/user for all queues
users {*} to slots=840
Limit slots/user for hiMem queues
users {*} queues {sThM.q} to slots=840
users {*} queues {mThM.q} to slots=585
users {*} queues {lThM.q} to slots=390
users {*} queues {uThM.q} to slots=73
Limit slots/user for xlMem restricted queue
users {*} queues {uTxlM.rq} to slots=536
Limit total reserved memory for all users per queue type
users * queues sThC.q,mThC.q,lThC.q,uThC.q to mem_res=40902G
users * queues sThM.q,mThM.q,lThM.q,uThM.q to mem_res=36637G
users * queues uTxlM.rq to mem_res=8063G
Limit reserved memory per user for specific queues
users {*} queues sThC.q,mThC.q,lThC.q,uThC.q to mem_res=10225G
users {*} queues sThM.q,mThM.q,lThM.q,uThM.q to mem_res=9159G
users {*} queues uTxlM.rq to mem_res=8063G
Limit slots/user for interactive (qrsh) queues
users {*} queues {qrsh.iq} to slots=16
Limit GPUs for all users in GPU queues to the avail no of GPUs
users * queues {sTgpu.q,mTgpu.q,lTgpu.q,qgpu.iq} to GPUS=8
Limit GPUs per user in all the GPU queues
users {*} queues sTgpu.q,mTgpu.q,lTgpu.q,qgpu.iq to GPUS=4
Limit GPUs per user in each GPU queues
users {*} queues {sTgpu.q} to GPUS=4
users {*} queues {mTgpu.q} to GPUS=3
users {*} queues {lTgpu.q} to GPUS=2
users {*} queues {qgpu.iq} to GPUS=1
Limit to set aside a slot for blast2GO
users * queues !lTb2g.q hosts {@b2g-hosts} to slots=110
users * queues lTb2g.q hosts {@b2g-hosts} to slots=1
users {*} queues lTb2g.q hosts {@b2g-hosts} to slots=1
Limit total bigtmp concurrent request per user
users {*} to big_tmp=25
Limit total number of idl licenses per user
users {*} to idlrt_license=102
Limit slots for io queue per user
users {*} queues {lTIO.sq} to slots=8
Limit slots for io queue per user
users {*} queues {lTWFM.sq} to slots=2
Limit the number of concurrent jobs per user for some queues
users {*} queues {uTxlM.rq} to no_concurrent_jobs=3
users {*} queues {lTIO.sq} to no_concurrent_jobs=2
users {*} queues {lWFM.sq} to no_concurrent_jobs=1
users {*} queues {qrsh.iq} to no_concurrent_jobs=4
users {*} queues {qgpu.iq} to no_concurrent_jobs=1
Limit slots/user in hiCPU queues
users {*} queues {sThC.q} to slots=840
users {*} queues {mThC.q} to slots=840
users {*} queues {lThC.q} to slots=431
users {*} queues {uThC.q} to slots=143
You can view plots of disk use vs time, for the past 7, 30, or 120 days;
as well as
plots of disk usage by user, or
by device (for the past 90 or 240 days respectively).
Notes
Capacity shows % disk space full and % of inodes used.
When too many small files are written on a disk, the file system can become full because it is
unable to keep track of new files.
The % of inodes should be lower or comparable to the % of disk space used.
If it is much larger, the disk can become unusable before it gets full.