[tor-relays] Network Bandwidth Fine Tuning

[Sebastian Niehaus]

Am 29.02.2016 um 00:15 schrieb Moritz Bartl:

> It can take up to roughly a month before a new relay reaches its 'final'
> throughput levels. See
> https://blog.torproject.org/blog/lifecycle-of-a-new-relay for details.

I am surprised as well because my middle relay has quite a low traffic,
at least not as much a I expect.


https://atlas.torproject.org/#details/7A32C9519D80CA458FC8B034A28F5F6815649A98

Advertised Bandwidth: 7.74 MB/s but it should do more

It is quite a small box but always has free memory left:

niehaus at rocket:~$ vmstat
procs -----------memory---------- ---swap-- -----io---- -system--
------cpu-----
 r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy
id wa st
 0  0 185600  93328   4112  73220    0    1    11    12   61   21  5  4
91  0  0



The highes percentage of CPU use in top I have seen is about 15%, there
is quite a lot idle time left. AES is supported in hardware, network
speed is okay;

niehaus at rocket:~$ bin/speedtest-cli
Retrieving speedtest.net configuration...
Retrieving speedtest.net server list...
Testing from arsys.es (82.223.21.74)...
Selecting best server based on latency...
Hosted by Vodafone Spain (Madrid) [0.00 km]: 7.529 ms
Testing download speed........................................
Download: 385.85 Mbit/s
Testing upload speed..................................................
Upload: 242.09 Mbit/s
niehaus at rocket:~$

Anything I can do to donate more bandwith? Any more information you need?

-- 
Sebastian Niehaus
Am Freibad West 80
38440 Wolfsburg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20160302/1c620701/attachment.sig>