Sherlock changelog

www.sherlock.stanford.edu

Back to job #1, thrice

by Kilian Cavalotti, Technical Lead & Architect, HPC

Not once, not twice, but three times! For the third time in Sherlock’s history, the Slurm job ID counter was reset over the weekend, and went from job #67,043,327 all the way back to job #1! JobIDRaw Partition

Introducing a new service partition on Sherlock

by Kilian Cavalotti, Technical Lead & Architect, HPC

We’re very pleased to introduce a new service partition on Sherlock, specially designed to run non-computational management and administrative tasks. Jobs like data transfer tasks, backups, CI/CD pipelines, workflow managers, or

Introducing a new service partition on Sherlock

Sherlock 4.0: a new cluster generation

by Kilian Cavalotti, Technical Lead & Architect, HPC

We are thrilled to announce that Sherlock 4.0, the fourth generation of Stanford's High-Performance Computing cluster, is now live! This major upgrade represents a significant leap forward in our computing capabilities, offering researchers

Sherlock 4.0: a new cluster generation

Sherlock 4.0 is coming!

by Kilian Cavalotti, Technical Lead & Architect, HPC

We are thrilled to announce that the next generation of Stanford's High-Performance Computing cluster is just around the corner. Mark your calendars for August 29, as we prepare to unveil Sherlock 4.0! Building on the success of previous

Sherlock 4.0 is coming!

Instant lightweight GPU instances are now available

by Kilian Cavalotti, Technical Lead & Architect, HPC

We know that getting access to GPUs on Sherlock can be difficult and feel a little frustrating at times. Demand has been steadily growing, leading to long pending times, and waiting in line rarely feels great, especially when you have

Instant lightweight GPU instances are now available

A new tool to help optimize job resource requirements

by Kilian Cavalotti, Technical Lead & Architect, HPC

It’s not always easy to determine the right amount of resources to request for a computing job. Making sure that the application will have enough resources to run properly, but avoiding over-requests that would make the jobs spend too much

ClusterShell on Sherlock

by Kilian Cavalotti, Technical Lead & Architect, HPC

Ever wondered how your jobs were doing while they were running? Keeping a eye on a log file is nice, but what if you could quickly gather process lists, usage metrics and other data points from all the nodes your multi-node jobs are running

ClusterShell on Sherlock

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. JobID Partition Start ------------

A new interactive step in Slurm

by Kilian Cavalotti, Technical Lead & Architect, HPC

A new version of the sh_dev tool has been released, that leverages a recently-added Slurm feature. Slurm 20.11 introduced a new“interactive step”, designed to be used with salloc to automatically launch a terminal on an allocated compute

Newer