Hello All. Things are better at the moment (it's ~ 2:30 AM east coast time). But... Although an https clone no longer pegs my CPU at 100%, it still sucks:
$ time git clone https://git.savannah.gnu.org/r/gawk.git Cloning into 'gawk'... Fetching objects: 61396, done. real 11m34.265s user 0m39.351s sys 0m6.825s [gleep:pts/1 x]$ time git clone ssh://arn...@git.sv.gnu.org/srv/git/gawk.git Cloning into 'gawk'... remote: Counting objects: 61396, done. remote: Compressing objects: 100% (14478/14478), done. remote: Total 61396 (delta 48458), reused 58395 (delta 46267) Receiving objects: 100% (61396/61396), 64.77 MiB | 1.05 MiB/s, done. Resolving deltas: 100% (48458/48458), done. real 1m44.371s user 0m26.581s sys 0m1.931s Is an order of magnitude difference for https normal? Thanks, Arnold arn...@skeeve.com wrote: > Corwin Brust <cor...@bru.st> wrote: > > > On Tue, Jan 7, 2025 at 9:22 AM Eli Zaretskii <e...@gnu.org> wrote: > > > > > > > > > Thanks, looks like it got fixed now. > > > > > > > Thank you for reporting and for confirming things are working better > > now. FWIW we have recently added some sysops team-members in > > additional Timezones however we're still training and on-boarding > > people so coverage for Savannah (&ct.) is much better during US > > working hours for the time being. > > I'm not so sure it's fixed. An https git clone of the gawk repo is taking a > long time and has pegged one of my cores at 100%. The fan is going > like crazy. > > I was able to do ssh git pushes without problem. > > Thanks, > > Arnold
