That is correct. The architecture assumes that many of the jobs are "services",
which tend to run for long periods of time.
Deepak
On Thu, Apr 16, 2015 at 10:19 PM, Christopher Samuel
<sam...@unimelb.edu.au> wrote:
> On 17/04/15 02:26, Alex Chekholko wrote:
>> IIRC most of their jobs ran for just milliseconds, so as we've learned
>> many times before, the way they do things at Google may not really be
>> applicable to the rest of the world.
> Possibly, though a friend of mine who works there (and who pointed me at
> the paper) remarked (when I mentioned that the paper said that jobs
> could run "to a few days"):
> # it's what we use to run thousands of instances of permanent
> # jobs as well
> and:
> # in practice I regularly have tasks run months
> All the best,
> Chris
> --
> Christopher Samuel Senior Systems Administrator
> VLSCI - Victorian Life Sciences Computation Initiative
> Email: sam...@unimelb.edu.au Phone: +61 (0)3 903 55545
> http://www.vlsci.org.au/ http://twitter.com/vlsci
> _______________________________________________
> Beowulf mailing list, Beowulf@beowulf.org sponsored by Penguin Computing
> To change your subscription (digest mode or unsubscribe) visit
> http://www.beowulf.org/mailman/listinfo/beowulf
_______________________________________________
Beowulf mailing list, Beowulf@beowulf.org sponsored by Penguin Computing
To change your subscription (digest mode or unsubscribe) visit
http://www.beowulf.org/mailman/listinfo/beowulf
