Sherlock changelog

Doubling the FLOPs, another milestone for Sherlock's performance

by Kilian Cavalotti, Technical Lead & Architect, HPC
Hardware
Event
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

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

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

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,
New
Training

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

๐ŸŽ‰ 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[1], started running its first job in January 2017. Fifty million jobs in less than 3 years is no

Search fix on the documentation website

by Sherlock Team
We're glad if you didn't notice, but in case you did, the Search feature on the documentation pages had some issues when searching for complete or capitalized words. It's all fixed now, so you can open the search box (a simple key press on
Fix