I try to avoid the phrase “cloud bursting” now, for precisely this reason.
Many of my users have heard the phrase, and think it means they’ll be able to
instantly start work in the cloud, just because the local cluster is busy. On
the compute side, yes, it’s pretty quick but as you say, getting the data out
there is time consuming, and if you keep it out there all the time, expensive.
Tim
On 26 Jul 2019, at 05:00, Joe Landman
<joe.land...@gmail.com<mailto:joe.land...@gmail.com>> wrote:
The issue is bursting with large data sets. You might be able to pre-stage
some portion of the data set in a public cloud, and then burst jobs from there.
Data motion between sites is going to be the hard problem in the mix. Not
technically hard, but hard from a cost/time perspective.
--
The Wellcome Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.
_______________________________________________
Beowulf mailing list, Beowulf@beowulf.org sponsored by Penguin Computing
To change your subscription (digest mode or unsubscribe) visit
https://beowulf.org/cgi-bin/mailman/listinfo/beowulf
