timestamp1679706261451A new tool to help optimize job resource requirementsby Kilian Cavalotti, Technical Lead & Architect, HPCIt’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
timestamp1667700685989Job #1, again!by Kilian Cavalotti, Technical Lead & Architect, HPCThis 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.
timestamp16174080000003.3 PFlops: Sherlock hits expansion milestoneby Kilian Cavalotti, Technical Lead & Architect, High Performance ComputingHardwareEventSherlock 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
timestamp1612549200000Tracking NFS problems down to the SFP levelby Kilian CavalottiBlogDataHardwareWhen NFS problems turn out to be... not NFS problems at all.
timestamp1589822580001New Sherlock on-boarding sessionsby Kilian CavalottiOne 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...
timestamp1589227740001Job #1by Kilian CavalottiIf 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...
Subscribe to updatesSubscribe to updates