> On 28 Jun 2017, at 15:39, Vort <vvort@xxxxxxxxx> wrote: > ... >> What is the connection / handle limit on the tor process and the user >> you are using for the tor process? > >> For a non-exit relay, it needs to be around 10,000. >> For an large exit relay, it needs to be 50,000 or so. > > Windows does not limit connection count for processes and users. > There are also no system-wide limit for sockets. > Except for available dynamic port range (1025-64510 on my computer). Depending on your Windows version, the limit may be around 2000-4000, check this article: http://smallvoid.com/article/winnt-tcpip-max-limit.html You should also check how many connections your relay is actually making. >> Now check the latency and bandwidth to these directory authorities. >> But only do to once, they have a lot of load already. > >> Also, use gabelmoobwauth, rather than gabelmoo. >> And check Faravahar. > > Latency (ping): > longclaw / 199.254.238.53 : 187 ms > gabelmoobwscan / 131.188.40.189 : 44 ms > moria1 / 128.31.0.34 : 128 ms > faravahar / 154.35.175.225 : 147 ms > > Bandwidth (via PrivacyRepublic0001 and 16M file from 38.229.72.16): > longclaw : 285 KiB/s > gabelmoobwscan : 1195 KiB/s > moria1 : 404 KiB/s > faravahar : 141 KiB/s Ok, so if your relay is in the 16MB bucket, it should be measured at at least 200 after a few weeks. But it's hard to tell which bucket each relay is in, that depends on the bandwidth authority. >> Ok, the next limit will be the observed bandwidth. > > After the yesterday test #5, observed bandwidth changed to 1.12 MiB/s. That might unstick your relay. We need to know if this happens, because it helps us to know what to do to fix stuck relays. >> You need to be patient. > > That's not a problem if I know that something will definitely > change in the future. We are working on it a few different ways: * increasing the minimum bandwidth authority file size * making an automatic process to un-stick stuck relays * getting more bandwidth authorities in more places * re-writing the bandwidth authority code 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 ------------------------------------------------------------------------
Attachment:
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays