Marc Glisse <marc.gli...@inria.fr> writes: One thing that should be doable is set up a mirror of GMP's repository on github, and advertise that one for CI purposes. Any user could do that (there are already a few), but if it was advertised on the GMP website, it would be more likely to be used by more people. Of course it would be good if people didn't set up their CI in such a wasteful way, but the trend doesn't make me very optimistic.
We don't now if Mike Blacker's message is completely accurate. I assume it was worded by a lawyer: the abusive traffic is not the fault of any large corporation, the fault lies with "a user" and...the victim of the abusive traffic. It is abundantly clear that neither Github nor Microsoft think they need to do anything about this, The traffic continues as I write this; in fact we had to add a few more Microsoft IP ranges to our firewall this morning. We certainly could make our infrastructure more resilient to this type of abusive traffic. The repo requests currently is handled by a single CPU core, and that has worked fine for a very long time, but with a clone request every few seconds hour after hour, that CPU get bogged down by running compressions. So how many CPU cores should we assign to this? Clearly, if the abusive traffic just scaled up a little, no number of CPU cores would suffice. -- Torbjörn Please encrypt, key id 0xC8601622 _______________________________________________ gmp-devel mailing list gmp-devel@gmplib.org https://gmplib.org/mailman/listinfo/gmp-devel
