Translations:META-Farm/142/en: Difference between revisions

← Older edit

Translations:META-Farm/142/en (view source)

Revision as of 18:31, 21 March 2023

4 bytes removed , 1 year ago

Importing a new version from external source

FuzzyBot

Bots

38,760

edits

@@ Line 1: / Line 1: @@
 The META package has important advantages over other approaches like [[GLOST]] where farm processing is done by bundling up all the jobs into a large parallel (MPI) job:
 * As the scheduler has full flexibility to start individual metajobs when it wants, the queue wait time can be dramatically shorter with the META package than with GLOST. Consider a large farm where 1000 CPU cores need to be used for 3 days;
-** with META, some metajobs start to run and produce the first results within minutes;
+** with GLOST, with a 1000-way MPI job, queue wait time can be weeks, so it'll be weeks before you see your very first result;
-** with GLOST, with a 1000-way MPI job, queue wait time can be weeks, so it'll be weeks before you see your very first result.
+** with META, some metajobs start to run and produce the first results within minutes.
-* With GLOST, at the end of the farm computations, some MPI ranks will finish earlier and will sit idle until the very last—the slowest—MPI rank ends. In the META package, there is no such waste at the end of the farm: individual metajobs exit earlier if they have no more workload to process.
+* At the end of the farm computations;
+** with GLOST, some MPI ranks will finish earlier and will sit idle until the very last—the slowest—MPI rank ends;
+** with META, there is no such waste at the end of the farm: individual metajobs exit earlier if they have no more workload to process.
 * GLOST and other similar packages do not support automated resubmission of the cases which failed or never ran. META has this feature, and it is very easy to use.