Sherlock changelog

Sherlock changelog

www.sherlock.stanford.edu

Storage quota units change: TB to TiB

by Kilian Cavalotti, Technical Lead & Architect, HPC
Following in Oak footsteps, we’re excited to announce that Sherlock is adopting a new unit of measure for file system quotas. Starting today, we're transitioning from Terabytes (TB) to Tebibytes (TiB) for all storage allocations on
Improvement
Data

Sherlock goes full flash

by Stéphane Thiell & Kilian Cavalotti, Research Computing Team
Data
Hardware
Improvement
What could be more frustrating than anxiously waiting for your computing job to finish? Slow I/O that makes it take even longer is certainly high on the list. But not anymore! Fir, Sherlock’s scratch file system, has just undergone a major
Sherlock goes full flash

Job #1, again!

by Kilian Cavalotti, Technical Lead & Architect, HPC
This is not the first time, we’ve been through this already (not so long ago, actually) but today, the Slurm job id counter was reset and went from job #67043327 back to job #1.
Event
Scheduler

3.3 PFlops: Sherlock hits expansion milestone

by Kilian Cavalotti, Technical Lead & Architect, High Performance Computing
Hardware
Event
Sherlock is a traditional High-Performance Computing cluster in many aspects. But unlike most of similarly-sized clusters where hardware is purchased all at once, and refreshed every few years, it is in constant evolution. Almost like a
3.3 PFlops: Sherlock hits expansion milestone

Tracking NFS problems down to the SFP level

by Kilian Cavalotti
Blog
Data
Hardware
When NFS problems turn out to be... not NFS problems at all.
Tracking NFS problems down to the SFP level

Sherlock facts

by Kilian Cavalotti
Data
Improvement
Ever wondered how many compute nodes is Sherlock made of? Or how many users are using it? Or how many Infiniband cables link it all together? Well, wonder no more: head to the Sherlock facts page and see for yourself! > hint: there are...
Sherlock facts

New Sherlock on-boarding sessions

by Kilian Cavalotti
One of the most requested improvements around Sherlock services, that came out of our recent user survey, was for more documentation and more training. This is why, to help new users get familiar with Sherlock's computing environment...
New
Training