Currently, in the framework each tasks has nJobs on scale:
Production
InputFileTask (nDataset) -> AnaTupleFileTask (~nTotalFiles) -> AnaTupleFileListTask (nDataset) -> AnaTupleMergeTask (~nTotalFiles) -> [ optional AnalysisCacheTask (~nTotalFiles) ]
Plotting
HistTupleProducerTask (nTotalFiles) -> HistFromNtupleProducerTask (nDataset * nVariables) -> HistMergerTask (nVariables) -> HistPlotTask (nVariables)
This means that the number of jobs per task varies greatly. To reduce batch jobs, generally you can run with tasks-per-job 10 for tasks until HistMergerTask. After that, HistMergerTask and HistPlotTask can be run with tasks-per-job 1.
Suggestion is to add a default value for tasks-per-job, making it easier to simply submit HistPlotTask while still being reasonable to nJobs for batch submission.
Currently, in the framework each tasks has nJobs on scale:
Production
InputFileTask (nDataset) -> AnaTupleFileTask (~nTotalFiles) -> AnaTupleFileListTask (nDataset) -> AnaTupleMergeTask (~nTotalFiles) -> [ optional AnalysisCacheTask (~nTotalFiles) ]
Plotting
HistTupleProducerTask (nTotalFiles) -> HistFromNtupleProducerTask (nDataset * nVariables) -> HistMergerTask (nVariables) -> HistPlotTask (nVariables)
This means that the number of jobs per task varies greatly. To reduce batch jobs, generally you can run with
tasks-per-job 10for tasks untilHistMergerTask. After that,HistMergerTaskandHistPlotTaskcan be run withtasks-per-job 1.Suggestion is to add a default value for
tasks-per-job, making it easier to simply submitHistPlotTaskwhile still being reasonable to nJobs for batch submission.