> On 4 Jan 2018, at 08:52, r1610091651 <r1610091651@telenet.be> wrote:
>
> Outcome of a script to count # connections /24 range
>
>
>      11 188.214.30.*
>      20 37.48.104.*
>      22 37.48.86.*
>      33 5.79.72.*
>      48 212.32.226.*
>      97 212.32.239.*
>     197 149.202.66.*
>     294 5.79.103.*
>     303 198.7.59.*
>     358 207.244.110.*
>     380 162.210.192.*
>     394 207.244.70.*
>     395 199.115.112.*
>     499 54.36.51.*
>
> And that on my lowly relay (consesus of 1k)
>
> Other relays seeing this too?

Yes, there are about a million extra clients on the network since
December. See this email for details:

https://lists.torproject.org/pipermail/tor-relays/2017-December/014002.html

If this is causing your relay issues, here are the things you can try:

RAM:

Set MaxMemInQueues to half your available RAM per tor instance.
(It doesn't track all of Tor's memory usage.)

If your machine has one relay, if you have this much RAM, try this setting:
4 GB -> MaxMemInQueues 512 MB
8 GB -> MaxMemInQueues 2 GB
16 GB -> MaxMemInQueues 4 GB
32 GB -> MaxMemInQueues 8 GB

(If you have more than one relay on the machine, divide MaxMemInQueues by the
number of relays. If you still have RAM issues, take down one relay.)

File descriptors / sockets:

Increase file descriptors for your tor user, or set ConnLimit to the
number of file descriptors available to tor.

CPU:

Set MaxAdvertisedBandwidth lower to shift client load to other relays.

T

--
Tim Wilson-Brown (teor)

teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org
------------------------------------------------------------------------



_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays