<div dir="ltr">Hi Thomas,<div><br></div><div>Adam and I discussed and I agree with his points. His "patchseries apply" script rewrite will already alleviate this issue to a significant degree, but it will be even better if we can also use next-* mirrors on GitHub. Do you know who I can contact about this?</div><div><br></div><div>Also, as of today our LTS testing is now moved over to GitHub, which should help a little. </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Nov 27, 2023 at 4:30 PM Adam Hassick <<a href="mailto:ahassick@iol.unh.edu">ahassick@iol.unh.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div><div><div><div>Hi Thomas,<br><br></div>Yes, mirroring the next-* branches would help to reduce the complexity of creating patch series artifacts.<br>As Patrick wrote, moving the clones for the periodic testing on DPDK main and DPDK LTS should be a trivial change.<br><br></div>However, most of the load we put on that server originates from our testing on new patch series.<br>I am working on a new script for creating the tarball artifacts from incoming patch series. It only pulls down either 1 or 2 repositories rather than main and all next-* branches for every single patch.<br>Once deployed, I expect this script to reduce the load on <a href="http://git.dpdk.org" target="_blank">git.dpdk.org</a> significantly.<br>Also, I anticipate that I can modify this new script to pull main down from GitHub. Then, only incoming patch series for next-* branches will produce any load on <a href="http://git.dpdk.org" target="_blank">git.dpdk.org</a>.<br></div><div><br></div>Thanks,<br></div>Adam Hassick<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Nov 27, 2023 at 3:58 PM Thomas Monjalon <<a href="mailto:thomas@monjalon.net" target="_blank">thomas@monjalon.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">27/11/2023 17:09, Patrick Robb:<br>
> Hello,<br>
> <br>
> Thanks for the heads up Thomas. For the Community Lab, as far as I can<br>
> tell, every git clone/fetch for DPDK main and DPDK LTS should be able to be<br>
> moved to the GitHub repo.<br>
> <br>
> On the other hand, I don't think next-* branches are mirrored on GitHub (at<br>
> least for now), so unless I'm mistaken, we will still have to pull from<br>
> <a href="http://git.dpdk.org" rel="noreferrer" target="_blank">git.dpdk.org</a>. But, between DPDK main and LTS, it should still be a sizable<br>
> reduction on the load put on your server. I'll discuss with the team today<br>
> and we will update here.<br>
<br>
We should mirror next-* trees as well I think, good point.<br>
<br>
<br>
> On Mon, Nov 27, 2023 at 6:21 AM Thomas Monjalon <<a href="mailto:thomas@monjalon.net" target="_blank">thomas@monjalon.net</a>> wrote:<br>
> <br>
> > Hello,<br>
> ><br>
> > The server <a href="http://git.dpdk.org" rel="noreferrer" target="_blank">git.dpdk.org</a> is not strong enough to hold all CI requests.<br>
> > When a script is doing a git fetch or clone, it is consuming workload on<br>
> > the server.<br>
> > Please could you favor the mirror on GitHub in any CI automation?<br>
> > <a href="https://github.com/DPDK/dpdk.git" rel="noreferrer" target="_blank">https://github.com/DPDK/dpdk.git</a><br>
> > This mirror is updated as frequently as <a href="http://git.dpdk.org" rel="noreferrer" target="_blank">git.dpdk.org</a>:<br>
> > We push to <a href="http://git.dpdk.org" rel="noreferrer" target="_blank">git.dpdk.org</a> where a git hook is replicating the same on<br>
> > GitHub.<br>
> ><br>
> > Hope we can reduce the workload on our main server.<br>
> > Thank you everyone for collaborating.<br>
<br>
<br>
<br>
</blockquote></div></div>
</blockquote></div><br clear="all"><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><p dir="ltr" style="line-height:1.2;margin-top:0pt;margin-bottom:0pt"><font color="#000000" face="Arial"><span style="font-size:13.3333px;white-space:pre-wrap">Patrick Robb</span></font></p><p style="color:rgb(34,34,34);line-height:1.2;margin-top:0pt;margin-bottom:0pt"><span style="font-size:10pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">Technical Service Manager</span></p><p dir="ltr" style="color:rgb(34,34,34);line-height:1.2;margin-top:0pt;margin-bottom:0pt"><span style="font-size:10pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">UNH InterOperability Laboratory</span></p><p dir="ltr" style="color:rgb(34,34,34);line-height:1.2;margin-top:0pt;margin-bottom:0pt"><span style="font-size:10pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">21 Madbury Rd, Suite 100, Durham, NH 03824</span></p><p dir="ltr" style="color:rgb(34,34,34);line-height:1.2;margin-top:0pt;margin-bottom:0pt"><span style="font-size:10pt;font-family:Arial;color:rgb(17,85,204);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><a href="http://www.iol.unh.edu/" style="color:rgb(17,85,204)" target="_blank">www.iol.unh.edu</a></span></p><p dir="ltr" style="color:rgb(34,34,34);line-height:1.2;margin-top:0pt;margin-bottom:0pt"><br></p><p dir="ltr" style="color:rgb(34,34,34);line-height:1.2;margin-top:0pt;margin-bottom:0pt"><span style="font-size:10pt;font-family:Arial;color:rgb(51,51,51);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><img src="https://lh4.googleusercontent.com/7sTY8VswXadak_YT0J13osh5ockNVRX2BuYaRsKoTTpkpilBokA0WlocYHLB4q7XUgXNHka6-ns47S8R_am0sOt7MYQQ1ILQ3S-P5aezsrjp3-IsJMmMrErHWmTARNgZhpAx06n2" width="150" height="37" style="border: none;"></span></p></div></div>