<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div>Dear FX,<div class="">We have the capability monitoring the resources used by individual accounts as part of the SciComp tools. These are tools accessible to everyone from theSciComp page. The monitoring is indicating the resources used by RG-K over the last week exceed largely what was used by RG-B. I don’t think we are lacking in terms of tools here and I’m not sure I understand the motivation of this concern. <div class="">We can discuss this further but I’m not sure this aspect is really central to decide how the RG-K and RG-B cooking should continue. The plan defined by the CCC for the data processing was 1) to run in parallel for about a week, while RGK was a still in testing phase, 2) continue with RG-K alone until the 50% was reached, 3) continue in parallel till the end. It seems to me that we basically skipped 1 because the fairshare algorithm did what it is designed to do, we are in 2, and the natural thing would be to continue with 3. This would be compliant to the CCC indications and the most efficient solution from the technical point of view.</div><div class="">Obviously the CCC can reconsider the situation and provide different indications: I have cc’ed Kyungseon and Marco if they want to comment.</div><div class="">Best regards,</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>Raffaella</div><div class=""><br class=""></div><div class=""><br class=""></div></div></div><div><blockquote type="cite" class=""><div class="">On 31 Jul 2020, at 16:12, Francois-Xavier Girod <<a href="mailto:fxgirod@jlab.org" class="">fxgirod@jlab.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Dear Raffaella<div class=""><br class=""></div><div class="">> During last week, the RG-B cooking, even if not fully stopped, progressed at a very slow rate because the farm fairshare algorithm favored the RG-K account that was not used in a while. Because of this, RG-K has been basically running alone for most of the time as for example it’s happening right now.</div><div class=""><br class=""></div><div class="">Do we have the tools to monitor how many CPU hours were used by what account?</div><div class="">If we do not have these tools, is the only monitoring available the throughput accomplished by one group vs another?</div><div class=""><br class=""></div><div class="">It seems to me that this is not a good situation for the collaboration. We should anticipate that there will be requests in the future to cook again, possibly even RGA, once we have improvement to the software released, such as ongoing work on the tracking.</div><div class=""><br class=""></div><div class="">I had understood that the RGK - RGB parallel cooking was a dry run to improve our preparedness against these issues. If we are not making progress on understanding the details of parallel cooking, it appears mysterious what the point of refusing our request. Whether RGK gets 100% of the ressources for 4 days or 50% of the resources for the 8 days, or even 25% of the resources for 16 days should make 0 difference whatsoever to RGB, unless they will be done in less than 16 days. </div><div class=""><br class=""></div><div class="">What is essential however is that we develop better tools to monitor the shared usage of resources, because these issues will only get worse.</div><div class=""><br class=""></div><div class="">Best regards</div><div class="">FX </div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jul 31, 2020 at 10:05 PM Raffaella De Vita <<a href="mailto:Raffaella.Devita@ge.infn.it" class="">Raffaella.Devita@ge.infn.it</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Dear Annalisa,<br class="">
As you mentioned the data processing has been progressing very well and, in about a week, we are already very closed to 50% of whole RG-K with the 7.5 GeV almost completed and the 6.5 GeV already started. At this pace, it looks like the 50% will be reached and exceeded over the weekend. <br class="">
<br class="">
During last week, the RG-B cooking, even if not fully stopped, progressed at a very slow rate because the farm fairshare algorithm favored the RG-K account that was not used in a while. Because of this, RG-K has been basically running alone for most of the time as for example it’s happening right now.<br class="">
<br class="">
Given this and considering the overall status, I think the 50% goal will be exceeded shortly, entering in what was defined as phase3 where both RG-K and RG-B can continue data processing in parallel. <br class="">
Best regards,<br class="">
Raffaella<br class="">
<br class="">
<br class="">
> On 31 Jul 2020, at 13:57, Annalisa D'Angelo <<a href="mailto:annalisa.dangelo@roma2.infn.it" target="_blank" class="">annalisa.dangelo@roma2.infn.it</a>> wrote:<br class="">
> <br class="">
> Dear Nathan and Raffaella,<br class="">
> <br class="">
> as you may see from the monitoring information at:<br class="">
> <br class="">
> <a href="https://clas12mon.jlab.org/files/?RGK7.5GeV" rel="noreferrer" target="_blank" class="">https://clas12mon.jlab.org/files/?RGK7.5GeV</a><br class="">
> <br class="">
> the pass1 cooking process of 7.5 GeV data has started last Friday night July 24th in parallel with RG-B.<br class="">
> <br class="">
> It been going quite efficiently this week so that we already have produced 88% of RG-K data at 7.5 GeV, corresponding to 44% of the full RG-K set of collected data.<br class="">
> <br class="">
> The agreement was that RG-K would run in parallel with RG-B for one week, and then alone for about another week to obtain 50% of the processed data.<br class="">
> <br class="">
> How should we interpret the next step ? May we run alone ?<br class="">
> <br class="">
> Thank you for your help and support, in particular to Nathan, who kindly agreed to launch and monitor the 6.5 GeV work flow.<br class="">
> <br class="">
> All the best<br class="">
> <br class="">
> Annalisa<br class="">
> <br class="">
> -- <br class="">
> <br class="">
> ================================================<br class="">
> Prof. Annalisa D'Angelo<br class="">
> Dip. Fisica, Universita' di Roma "Tor Vergata"<br class="">
> Istituto Nazionale di Fisica Nucleare<br class="">
> Sezione di Roma Tor Vergata, Rome Italy<br class="">
> <a href="mailto:email%3Aannalisa.dangelo@roma2.infn.it" target="_blank" class="">email:annalisa.dangelo@roma2.infn.it</a><br class="">
> Jefferson Laboratory, Newport News, VA USA<br class="">
> Email: <a href="mailto:annalisa@jlab.org" target="_blank" class="">annalisa@jlab.org</a><br class="">
> Tel: + 39 06 72594562<br class="">
> <br class="">
> <br class="">
> <br class="">
<br class="">
<br class="">
<br class="">
_______________________________________________<br class="">
clas12_rgk mailing list<br class="">
<a href="mailto:clas12_rgk@jlab.org" target="_blank" class="">clas12_rgk@jlab.org</a><br class="">
<a href="https://mailman.jlab.org/mailman/listinfo/clas12_rgk" rel="noreferrer" target="_blank" class="">https://mailman.jlab.org/mailman/listinfo/clas12_rgk</a><br class="">
</blockquote></div>
</div></blockquote></div><br class=""></div></body></html>