Hacker News new | ask | show | jobs
by seized 1052 days ago
The latency is higher so the key is parallelism... Which means you need more cores/hardware/VMs/pick your poison. New but same problem...
1 comments

Is single-job performance the only criterion? Or can you just run a bunch of different jobs at the same time (genomics has many embarassingly parallel problems, often per-sample) and use the higher aggregate storage bandwidth of your object store to get "more work done in unit time".
I did the latter, across usually about 4000+ CPUs. That got me a peak of 15 or so GB/sec read from one GCS bucket, writing to another.

But yeah if it's not something that can be paralleled then it sucks.