Hi,
We are starting to move our workstations to a master/worker config with one of our workstations acting as a master and the rest as workers. This seems very nice and we are able to send jobs to the desired worker by selecting the target GPU.
The only problem that I have noticed is with CPU only jobs, for example when extracting from micrographs if one has a lot of CPUs available this can be faster than with GPUs. It would be nice if it would also be possible to direct these CPU only jobs to the same worker where the micrographs are stored for example.
Thank you for considering this feature request.
Thanks for your feature suggestion @jcoleman.
A workaround in recent releases might be to reassign nodes with special CPU capabilities to their dedicated scheduler lane. The drawback would be that such reassignment would remove a node from its current lane, and thus from its current lane’s pool of resources.
Suppose the “CPU-heavy” worker cpuworker.local is already connected as a worker to the CryoSPARC master server at csmaster.local running on port 61000. Then one could move the worker to its dedicated, new lane cpuworkers with the command (run on cpuworker.local):
/path/to/cryosparc_worker/bin/cryosparcw connect --update \
--master csmaster.local --port 61000 \
--worker cpuworker.local --newlane --lane cpuworkers
Please ensure that such an assignment does not leave behind an empty lane (of which the reassigned worker was a member previously.)