Sherlock changelog

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

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

More (and easier!) GPU scheduling options

by Kilian Cavalotti
New
Scheduler
Improvement
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...

🎉 Job #50,000,000!

by Kilian Cavalotti
Event
We just wanted to share that Sherlock recently ran job #50,000,000! 🎈🎉 This is a significant milestone since Sherlock, in its current form, started running its first job in January 2017. Fifty million jobs in less than 3 years is no...

A better view at Sherlock's resources

by Kilian Cavalotti
Scheduler
Improvement
New
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...

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

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

High priority QOS for owners

by Kilian Cavalotti
Today, we're introducing a new high-priority QOS for owner partitions. In groups which have purchased their own compute nodes on Sherlock, users can now submit jobs to their group partition using the --qos=high_p option: it will give...
Improvement
Scheduler