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
1hr.
Usage
Current snapshot sorted by nodes'
.
Usage vs time, for length=
and user=
highlighted.
As of Fri Oct 24 10:17:03 2025: #CPUs/nodes 5740/74, 0 down. Loads:
head node: 0.93, login nodes: 3.18, 0.08, 0.03, 0.03; NSDs: 0.08, 0.01, 0.21, 4.22, 3.35; licenses: none used.
Queues status: 9 disabled, none need attention, none in error state.
17 users with running jobs (slots/jobs):
Total number of queued jobs/tasks/slots: 3/3,512/8,762
60 users have/had running or queued jobs over the past 7 days, 77 over the past 15 days.
112 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 Friday, 24-Oct-2025 10:22:07 EDT
with mk-webpage.pl ver. 7.3/1 (Oct 2025/SGK) in 0:56.
Warnings
Oversubscribed Jobs
As of Fri Oct 24 10:17:03 EDT 2025 (1 oversubscribed job)
Total running (PEs/jobs) = 689/143, 3 queued (jobs), showing only oversubscribed jobs (cpu% > 133% & age > 1h) for all users.
jobID name user age nPEs cpu% queue node taskID
10967750 trim_galore_2 corderm +1:19 1 164.7% mThC.q 76-09
⇒ Equivalent to 0.6 overused CPUs: 1 CPUs used at 164.7% on average.
Inefficient Jobs
As of Fri Oct 24 10:17:04 EDT 2025 (18 inefficient jobs, showing no more than 3 per user)
Total running (PEs/jobs) = 689/143, 3 queued (jobs), showing only inefficient jobs (cpu% < 33% & age > 1h) for all users.
jobID name user age nPEs cpu% queue node taskID
11019047 filterallsky jhora 12:58 32 3.4% sThM.q 76-02
11019052 filtersky_W24_2 jhora 12:42 32 3.6% sThM.q 76-01
11019053 filtersky_W24_1 jhora 12:41 32 3.5% sThM.q 76-02
10961603 spades_5 santossam +1:21 20 8.0% mThM.q 64-17
10961789 spades_1 santossam +1:21 20 7.4% mThM.q 84-01
11016537 bffpens_coassem bornbuschs +1:02 16 6.9% lThM.q 76-12
10253677 Delphinidae_IQT mcgowenm +16:17 12 8.3% lThM.q 84-01
11019110 FST_10kb uribeje 01:41 4 24.6% uThM.q 76-08
11019111 FST_50kb uribeje 01:40 4 24.5% uThM.q 76-10
11019112 FST_50kb uribeje 01:39 4 24.8% uThM.q 64-18
(more by uribeje)
10947026 bears atkinsonga +2:00 1 0.2% lTWFM.sq 64-15
⇒ Equivalent to 186.6 underused CPUs: 205 CPUs used at 9.0% on average.
To see them all use:
'q+ -ineff -u uribeje' (10)
Nodes with Excess Load
As of Fri Oct 24 10:17:05 EDT 2025 (4 nodes have a high load, offset=1.5)
#slots excess
node #CPUs used load load
-----------------------------------
64-10 40 4 8.1 4.1 * 76-03 192 24 34.8 10.8 * 76-04 192 4 6.3 2.3 * 76-13 128 32 34.4 2.4 *Total excess load = 19.6
As of Fri Oct 24 10:17:05 EDT 2025
1 job waiting for breusingc:
jobID jobName user age nPEs memReqd queue taskID
--------- --------------- ---------------- ------ ---- -------- ------ -------
11017798 ReadFilter breusingc 21:52 16 64.0 mThC.q 53-402:1
quota rule resource=value/limit %used
------------------- ------------------------------- ------
max_slots_per_user/1 slots=160/840 19.0% for breusingc
max_hC_slots_per_user/2 slots=160/840 19.0% for breusingc in queue mThC.q
max_mem_res_per_user/1 mem_res=640.0G/9.985T 6.3% for breusingc in queue uThC.q
------------------- ------------------------------- ------
1 job waiting for coellogarridoa:
jobID jobName user age nPEs memReqd queue taskID
--------- --------------- ---------------- ------ ---- -------- ------ -------
11017815 raxml coellogarridoa 21:25 1 8.0 sThC.q 402-1013:1
quota rule resource=value/limit %used
------------------- ------------------------------- ------
max_slots_per_user/1 slots=100/840 11.9% for coellogarridoa
max_hC_slots_per_user/1 slots=100/840 11.9% for coellogarridoa in queue sThC.q
max_mem_res_per_user/1 mem_res=800.0G/9.985T 7.8% for coellogarridoa in queue uThC.q
------------------- ------------------------------- ------
1 job waiting for jbak:
jobID jobName user age nPEs memReqd queue taskID
--------- --------------- ---------------- ------ ---- -------- ------ -------
11016535 J_20220601T-uv3 jbak +1:02 1 mThC.q 1288-3837:1
none running.
Overall Quota Usage
quota rule resource=value/limit %used
------------------- ------------------------------- ------
blast2GO/1 slots=32/110 29.1% for *
total_slots/1 slots=689/5960 11.6% for *
total_mem_res/2 mem_res=3.862T/35.78T 10.8% for * in queue uThM.q
total_mem_res/3 mem_res=600.0G/7.874T 7.4% for * in queue uTxlM.rq
total_mem_res/1 mem_res=1.686T/39.94T 4.2% for * in queue uThC.q
Memory Usage
Reserved Memory, All High-Memory Queues
Select length:
Current Memory Quota Usage
As of Fri Oct 24 10:17:05 EDT 2025
quota rule resource=value/limit %used filter
---------------------------------------------------------------------------------------------------
total_mem_res/1 mem_res=1.686T/39.94T 4.2% for * in queue uThC.q
total_mem_res/2 mem_res=3.862T/35.78T 10.8% for * in queue uThM.q
total_mem_res/3 mem_res=600.0G/7.874T 7.4% for * in queue uTxlM.rq
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.