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

Introducing Boltz-1 on Sherlock

by Kilian Cavalotti, Technical Lead & Architect, HPC

We've received numerous inquiries about the availability of AlphaFold3 on Sherlock, and we understand the excitement surrounding this groundbreaking tool. AlphaFold, developed by DeepMind, revolutionized protein structure prediction and

Introducing Boltz-1 on Sherlock

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

Sherlock goes full flash

by Stéphane Thiell & Kilian Cavalotti, Research Computing Team

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

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

Keep up to date with software updates

by Kilian Cavalotti, Technical Lead & Architect, HPC

To help users stay on top of software changes on Sherlock, we’ve recently introduced a new software updates RSS feed. It’s available from the Sherlock software list page, and you can directly add it to your RSS reader of choice. And if

Newer