Re: [tor-relays] Recommended specifications for 1Gbps exit

2013-03-05 Thread mick
On Mon, 04 Mar 2013 18:37:01 +
Matt Joyce torad...@mttjocy.co.uk allegedly wrote:

 Of course being a server any contention is more likely going to be on
 the other side, but while I can find gigabit capable servers to try
 pulling from finding one to try pulling from me is entirely another
 story.  I did make a test file if anyone has the connection and 1GB of
 bw to try please let me know what you get
 http://torexit2.mttjocy.co.uk/1GBtest.bin
 

Matt

A thought. You could try for yourself using the same service I used at
https://www.digitalocean.com/features if you wanted to run some more
tests. Digital Ocean sell their droplets by the hour. So you could
easily fire up a test VM for less than the cost of a coffee and
doughnuts... 

Mick

-

blog: baldric.net
gpg fingerprint: FC23 3338 F664 5E66 876B  72C0 0A1F E60B 5BAD D312

-



signature.asc
Description: PGP signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


Re: [tor-relays] Recommended specifications for 1Gbps exit

2013-03-04 Thread mick
On Mon, 04 Mar 2013 18:37:01 +
Matt Joyce torad...@mttjocy.co.uk allegedly wrote:

 
 Of course being a server any contention is more likely going to be on
 the other side, but while I can find gigabit capable servers to try
 pulling from finding one to try pulling from me is entirely another
 story.  I did make a test file if anyone has the connection and 1GB of
 bw to try please let me know what you get
 http://torexit2.mttjocy.co.uk/1GBtest.bin
 

Here you go: http://rlogin.net/tor/torexit2.txt 

Deeply unscientific, but real world.

Mick

-

blog: baldric.net
gpg fingerprint: FC23 3338 F664 5E66 876B  72C0 0A1F E60B 5BAD D312

-



signature.asc
Description: PGP signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


Re: [tor-relays] Recommended specifications for 1Gbps exit

2013-03-04 Thread Steve Snyder


On 02/26/2013 08:46 AM, Matt Joyce wrote:

I am wondering if anyone with experience in this area could advise me
some on recommended specifications for a 1Gbps exit

[snip]

What DNS configuration will/are you using to handle the avalanche of 
resolution requests?

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


Re: [tor-relays] Recommended specifications for 1Gbps exit

2013-02-26 Thread Moritz Bartl
Hi Matt,

Tor indeed does not use more than one core for most of its operations,
effectively limiting throughput to ~100MBps per Tor process on a
non-AES-NI machine.

A CPU with AES-NI support can do up to 300-400MBps per Tor process.

You will have to run multiple Tor processes.

See https://www.torservers.net/wiki/setup/server#multiple_tor_processes
for a handy initscript.

On 26.02.2013 14:46, Matt Joyce wrote:
 I am wondering if anyone with experience in this area could advise me
 some on recommended specifications for a 1Gbps exit I think my latest
 once needs a package upgrade to handle it, currently seems stuck at
 around 100Mbps worth of traffic.  Currently it has access to 3 v cores
 @1.33Ghz and 1GB of RAM and I think the latter might be becoming the
 limit instead now I had thought it was the CPU when it had just the one
 core but that alone hasn't helped.
 
 I am not entirely sure if tor is infact using the other cores though
 watching with top it is sitting at 100 or a fraction over like 104% or
 so.  MaxCPU's is set in torrc to 4 as the OS sees 4 virtual cores but is
 capped to 300% by the hypervisor perhaps it should be set to 3 not sure
 if there is any benefit in setting to 4 I have limited experience with
 virtual servers but unfortunately a fully dedicated server for tor is
 financially out of my budget at the moment.
 
 Also, just to confirm while I'm aware it's very possible that the
 limitation could be bandwidth given it shares with the other VPS'es on
 the host I don't believe that was the case, I pulled a backup from there
 to another server of mine on a different AS and continent and it
 transferred at 250Mbps while tor was running at 100Mbps the entire time,
 so unless the contention is over the download which seems less likely
 for a server I think we should be able to get a good 300Mbps of exit
 capacity out of this possibly more.
 
 So can anyone can advise on recommended CPU, RAM have to consider budget
 but will try and meet them, also if there are any settings I should
 check in torrc?
 
 
 
 ___
 tor-relays mailing list
 tor-relays@lists.torproject.org
 https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
 

-- 
Moritz Bartl
https://www.torservers.net/
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


Re: [tor-relays] Recommended specifications for 1Gbps exit

2013-02-26 Thread Matt Joyce
Thanks, just set it up with 3 a few hours ago, will take a while before
starts advertising the full bandwidth again I guess.

I'm a little confused though for some reason only two of the instances
show up in atlas, the other one just keeps complaining it isn't in the
cached consensus and isn't seeing any usage either consensus health over
at metrics mentions that instance but nothing more it's reporting blank
for all of them what am I missing?

On 26/02/13 13:57, Moritz Bartl wrote:
 Hi Matt,

 Tor indeed does not use more than one core for most of its operations,
 effectively limiting throughput to ~100MBps per Tor process on a
 non-AES-NI machine.

 A CPU with AES-NI support can do up to 300-400MBps per Tor process.

 You will have to run multiple Tor processes.

 See https://www.torservers.net/wiki/setup/server#multiple_tor_processes
 for a handy initscript.

 On 26.02.2013 14:46, Matt Joyce wrote:
 I am wondering if anyone with experience in this area could advise me
 some on recommended specifications for a 1Gbps exit I think my latest
 once needs a package upgrade to handle it, currently seems stuck at
 around 100Mbps worth of traffic.  Currently it has access to 3 v cores
 @1.33Ghz and 1GB of RAM and I think the latter might be becoming the
 limit instead now I had thought it was the CPU when it had just the one
 core but that alone hasn't helped.

 I am not entirely sure if tor is infact using the other cores though
 watching with top it is sitting at 100 or a fraction over like 104% or
 so.  MaxCPU's is set in torrc to 4 as the OS sees 4 virtual cores but is
 capped to 300% by the hypervisor perhaps it should be set to 3 not sure
 if there is any benefit in setting to 4 I have limited experience with
 virtual servers but unfortunately a fully dedicated server for tor is
 financially out of my budget at the moment.

 Also, just to confirm while I'm aware it's very possible that the
 limitation could be bandwidth given it shares with the other VPS'es on
 the host I don't believe that was the case, I pulled a backup from there
 to another server of mine on a different AS and continent and it
 transferred at 250Mbps while tor was running at 100Mbps the entire time,
 so unless the contention is over the download which seems less likely
 for a server I think we should be able to get a good 300Mbps of exit
 capacity out of this possibly more.

 So can anyone can advise on recommended CPU, RAM have to consider budget
 but will try and meet them, also if there are any settings I should
 check in torrc?



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





signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


Re: [tor-relays] Recommended specifications for 1Gbps exit

2013-02-26 Thread Roger Dingledine
On Tue, Feb 26, 2013 at 11:54:59PM +, Matt Joyce wrote:
 I'm a little confused though for some reason only two of the instances
 show up in atlas, the other one just keeps complaining it isn't in the
 cached consensus and isn't seeing any usage either consensus health over
 at metrics mentions that instance but nothing more it's reporting blank
 for all of them what am I missing?

The tor consensus will only list at most 2 relays per IP address. So if
you want to run 4 relays, put them on two IP addresses.

https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/109-no-sharing-ips.txt

--Roger

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


Re: [tor-relays] Recommended specifications for 1Gbps exit

2013-02-26 Thread Matt Joyce
On 26/02/13 23:57, Roger Dingledine wrote:
 On Tue, Feb 26, 2013 at 11:54:59PM +, Matt Joyce wrote:
 I'm a little confused though for some reason only two of the instances
 show up in atlas, the other one just keeps complaining it isn't in the
 cached consensus and isn't seeing any usage either consensus health over
 at metrics mentions that instance but nothing more it's reporting blank
 for all of them what am I missing?
 The tor consensus will only list at most 2 relays per IP address. So if
 you want to run 4 relays, put them on two IP addresses.

 https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/109-no-sharing-ips.txt

 --Roger

 ___
 tor-relays mailing list
 tor-relays@lists.torproject.org
 https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Ah, looks like I will need to look at requesting another IP address,
again finding myself glad I asked the question rather than doing my
usual try to figure it out myself because I was at a complete loss.



signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays