Seven terabytes in three minutes
A real geospatial pipeline: 192,000 satellite files, resampled and written, start to finish.
Short walkthroughs: the mechanics, the common mistakes, and what the numbers actually look like.
A real geospatial pipeline: 192,000 satellite files, resampled and written, start to finish.
The shortest useful answer: write ordinary Python, get supercomputer throughput, skip the infrastructure.
Every panel in the browser IDE, what it controls, and which parts of your work survive a restart.
From an empty notebook to a running cluster and a completed task, including the blocking mistake almost everyone makes on their first fan-out.
What @eugo.hpc.distribute actually changes about a function, and why the call site stays clean.
The most common performance mistake in distributed code, and the two-line habit that avoids it.
Use .options() to ask for GPUs on the calls that need them, and only those.
Which array operations Eugo moves to the GPU on its own, and how to confirm it happened.
When a task is the wrong shape: keeping an expensive object alive across many calls.