For large enough projects, the boot disk may be insufficient to store all the downloaded images & generated QUPATH data.
In that case we can create a ramdisk (in-memory file-system) to leverage generally large amounts of RAM.
We currently limit to 1 task for node (b/c the GPU has to be dedicated). If we ever had more tasks per node, each would need this ramdisk space available…
QUESTION: do we actually need this? If we increase the boot disk size, we get this "for free". The main cost being of course the increased boot disk size that we currently use across tasks. And is RAM actually enough? I think the qupath code reloads the pieces from disk each time, that probably reduces RAM a lot.
So the RAM needs would be the (un?)compressed size of the images, plus, segmasks, plus, the uncompressed pixel overlay (1 float per pixel I think?). Then detection data…
Maybe for now, let's see how long we can get away with just using the default boot disk size.
For large enough projects, the boot disk may be insufficient to store all the downloaded images & generated QUPATH data.
In that case we can create a ramdisk (in-memory file-system) to leverage generally large amounts of RAM.
We currently limit to 1 task for node (b/c the GPU has to be dedicated). If we ever had more tasks per node, each would need this ramdisk space available…
QUESTION: do we actually need this? If we increase the boot disk size, we get this "for free". The main cost being of course the increased boot disk size that we currently use across tasks. And is RAM actually enough? I think the qupath code reloads the pieces from disk each time, that probably reduces RAM a lot.
So the RAM needs would be the (un?)compressed size of the images, plus, segmasks, plus, the uncompressed pixel overlay (1 float per pixel I think?). Then detection data…
Maybe for now, let's see how long we can get away with just using the default boot disk size.