Re: [tor-relays] Consensus Weight calculation

[Vort <vvort@xxxxxxxxx>]

> Before we investigate the measurements:
> * We need to know if anything on your relay or at your provider
>   is making your relay slow,
> * We need to be know which measurement of your relay is slow.

> I made a wiki page to tell people how to do that:
> https://trac.torproject.org/projects/tor/wiki/doc/MyRelayIsSlow

> Please go through the steps, and let us know what results you get.
> Then someone can help you more.

> 1. Check RAM, CPU, and socket/file descriptor usage on your relay

Private bytes amount for tor.exe process is 116 MiB,
  3.4 GiB of system memory is available (out of 8 GiB total).
Log shows that: "Based on detected system memory, MaxMemInQueues
  is set to 2048 MB. You can override this by setting MaxMemInQueues by hand."

Tor is using 0-1% of CPU resource on the average.
Sometimes it consumes 25% of CPU (100% of 1 core) for 10 seconds.
And then returns back to normal 0-1% usage.

Tor process have 573 handles open and about 380 established TCP
  connections. But this is unusual activity, related to Faravahar
  downtime and, respectively, obtaining of Fast and HSDir flags.
Usually, it have only 20-30 connections established.


> 2. Check the internet peering (bandwidth, latency) from your relay's
>   provider to other relays.

Latency (ping):
hviv104             / 192.42.116.16  : 40 ms
PrivacyRepublic0001 / 178.32.181.96  : 39 ms
Unnamed             / 185.170.41.8   : 36 ms
McCormickRecipes    / 18.85.22.204   : 135 ms
PhantomTrain4       / 65.19.167.131  : 184 ms

Bandwidth (via dopper / 192.42.113.102 and bwauth's 16M file):
hviv104                              : 50 KiB/s
PrivacyRepublic0001                  : 1.3 MiB/s
Unnamed                              : 155 KiB/s
McCormickRecipes                     : 947 KiB/s
PhantomTrain4                        : 899 KiB/s


> 3. Check each of the votes for your relay on consensus-health
>   (large page), and check the median:

Consensus was published 2017-06-27 12:00:00.
longclaw: bw=34
gabelmoo: bw=41
moria1  : bw=23

*median*: bw=34


> 4. Check your relay's observed bandwidth and bandwidth rate (limit).

Bandwidth rate    : 1 MiB/s
Bandwidth burst   : 3 MiB/s
Observed bandwidth: 250.77 KiB/s


> 5. Run a test using tor to see how fast tor can get on your network/CPU:

This will alter observed bandwidth. But okay.
Depending on exit node, result varies from 117 KiB/s to 1 MiB/s. Example:

$ curl --socks5-hostname localhost:9050 --insecure -O https://38.229.72.16/bwauth.torproject.org/16M
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 16.0M  100 16.0M    0     0   857k      0  0:00:19  0:00:19 --:--:--  967k


> 6. Run a test using tor and chutney to find out how fast tor can get on
>   your CPU. Keep increasing the data volume until the bandwidth stops increasing:

As this tool is designed for Linux, I can run it only within virtual machine.
But results are still good:

$ CHUTNEY_DATA_BYTES=104857600 ./chutney verify networks/basic-min
...
Single Stream Bandwidth: 99.46 MBytes/s
Overall tor Bandwidth: 397.85 MBytes/s

$ CHUTNEY_DATA_BYTES=1048576000 ./chutney verify networks/basic-min
...
Single Stream Bandwidth: 43.52 MBytes/s
Overall tor Bandwidth: 174.07 MBytes/s


> It might not be me that helps you.
> So please talk to the list when you write back.

But no one else shown the interest on answering to this topic.


-- Vort

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