timestamp1589227740001
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...timestamp1572984000001
More (and easier!) GPU scheduling options
by Kilian Cavalotti
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...timestamp1556922960001
A better view at Sherlock's resources
by Kilian Cavalotti
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...timestamp1541457360001
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...timestamp1537307580001
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...timestamp1533166320001
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...