<p dir="ltr">Maybe this article from the Tor FAQ will help: <a href="http://archives.seul.org/or/relays/Aug-2010/msg00034.html">http://archives.seul.org/or/relays/Aug-2010/msg00034.html</a></p>
<p dir="ltr">According to the article, Tor can only get 100Mbps per CPU core, and Tor doesn't use any more than 2 cores because it's not fully multithreaded. </p>
<p dir="ltr">You can only run 2 instances of Tor on the same IP address, which means a maximum of 800Mbps, if you do it right. </p>
<p dir="ltr">The answer from this link is pretty straightforward on how to run multiple instances: <a href="https://stackoverflow.com/questions/14321214/how-to-run-multiple-tor-processes-at-once-with-different-exit-ips">https://stackoverflow.com/questions/14321214/how-to-run-multiple-tor-processes-at-once-with-different-exit-ips</a></p>
<p dir="ltr">Just make sure you correctly set the MyFamily option in torrc, otherwise a client could (unlikely but possibly) use both of your instances in the same circuit. </p>
<div class="gmail_quote">On Mar 2, 2016 7:56 AM, "Sebastian Niehaus" <<a href="mailto:niehaus@web.de">niehaus@web.de</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Am 29.02.2016 um 00:15 schrieb Moritz Bartl:<br>
<br>
> It can take up to roughly a month before a new relay reaches its 'final'<br>
> throughput levels. See<br>
> <a href="https://blog.torproject.org/blog/lifecycle-of-a-new-relay" rel="noreferrer" target="_blank">https://blog.torproject.org/blog/lifecycle-of-a-new-relay</a> for details.<br>
<br>
I am surprised as well because my middle relay has quite a low traffic,<br>
at least not as much a I expect.<br>
<br>
<br>
<a href="https://atlas.torproject.org/#details/7A32C9519D80CA458FC8B034A28F5F6815649A98" rel="noreferrer" target="_blank">https://atlas.torproject.org/#details/7A32C9519D80CA458FC8B034A28F5F6815649A98</a><br>
<br>
Advertised Bandwidth: 7.74 MB/s but it should do more<br>
<br>
It is quite a small box but always has free memory left:<br>
<br>
niehaus@rocket:~$ vmstat<br>
procs -----------memory---------- ---swap-- -----io---- -system--<br>
------cpu-----<br>
r b swpd free buff cache si so bi bo in cs us sy<br>
id wa st<br>
0 0 185600 93328 4112 73220 0 1 11 12 61 21 5 4<br>
91 0 0<br>
<br>
<br>
<br>
The highes percentage of CPU use in top I have seen is about 15%, there<br>
is quite a lot idle time left. AES is supported in hardware, network<br>
speed is okay;<br>
<br>
niehaus@rocket:~$ bin/speedtest-cli<br>
Retrieving <a href="http://speedtest.net" rel="noreferrer" target="_blank">speedtest.net</a> configuration...<br>
Retrieving <a href="http://speedtest.net" rel="noreferrer" target="_blank">speedtest.net</a> server list...<br>
Testing from <a href="http://arsys.es" rel="noreferrer" target="_blank">arsys.es</a> (82.223.21.74)...<br>
Selecting best server based on latency...<br>
Hosted by Vodafone Spain (Madrid) [0.00 km]: 7.529 ms<br>
Testing download speed........................................<br>
Download: 385.85 Mbit/s<br>
Testing upload speed..................................................<br>
Upload: 242.09 Mbit/s<br>
niehaus@rocket:~$<br>
<br>
Anything I can do to donate more bandwith? Any more information you need?<br>
<br>
--<br>
Sebastian Niehaus<br>
Am Freibad West 80<br>
38440 Wolfsburg<br>
<br>
<br>_______________________________________________<br>
tor-relays mailing list<br>
<a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a><br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" rel="noreferrer" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br>
<br></blockquote></div>