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

Doubling the FLOPs, another milestone for Sherlock's performance

by Kilian Cavalotti, Technical Lead & Architect, HPC

We’re proud to announce that Sherlock has reached another significant performance milestone. Building on past successes, Sherlock continues to evolve and expand, integrating new technologies and enhancing its capabilities to meet the

Doubling the FLOPs, another milestone for Sherlock's performance

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

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

3.3 PFlops: Sherlock hits expansion milestone

by Kilian Cavalotti, Technical Lead & Architect, High Performance Computing

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

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,

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,000s.

🎉 Job #50,000,000!

by Kilian Cavalotti

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

🎉 Job #50,000,000!

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

Newer