Sherlock changelog

www.sherlock.stanford.edu

timestamp1667700685989

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.

timestamp1622751520986

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

timestamp1589822580001

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...

timestamp1589227740001

Job #1

by Kilian Cavalotti

If you've been submitting jobs on Sherlock over the last couple days, you probably noticed something different about your your job ids... They lost a couple digits! If you submitted a job last week, its job id was likely in the 67,000...

timestamp1572984000001

More (and easier!) GPU scheduling options

by Kilian Cavalotti

GPU scheduling is now easier and more powerful on Sherlock, with the addition of new job submission options especially targeted at GPU workloads. The most visible change is that you can now use the --gpus option when submitting jobs...

More (and easier!) GPU scheduling options

timestamp1556922960001

A better view at Sherlock's resources

by Kilian Cavalotti

How many jobs are running? What partitions do I have access to? How many CPUs can I use? Where should I submit my jobs? Any of those sound familiar? We know it's not always easy to navigate the native scheduler tools, their syntax, and...

A better view at Sherlock's resources

timestamp1541457360001

Persistent processes on Sherlock

by Kilian Cavalotti

There are many cases where having a persistent process (or service) running alongside computing jobs is of great benefit. For instance, when data is stored in a database format to allow for highly efficient queries, jobs that want to...

timestamp1539128040001

Running containers on Sherlock

by Kilian Cavalotti

Have you ever wanted to run Docker containers on Sherlock, and skip the hassle of figuring out your application dependencies, installing them, compiling the code, resolving compilation errors, finding missing libraries, or making sure...

Running containers on Sherlock

timestamp1537307580001

Better error messages when submitting jobs

by Kilian Cavalotti

Sherlock now offers a better and more complete explanation when a job submission is rejected by the scheduler. What does it look like? In the most common cases, jobs that don't meet the requirements for the partition they're submitted...