Hi Moritz,

im running a few high bandwidth relays, and i'm also interested in tuning the performance - at the moment i have experienced following things regarding AES-NI acceleration:

With an upgrade to ubuntu 13.10 x64 there seem to be no more support for aesni module - so it doesnt seem to be usable any more. With older ubuntu releases it works.
I've recognized that some configurations are running easily with an higher throughput - but could not figure out whats the reason for it.
My VPS'es are almost running in an KVM environment - but the 2 fastest ones running on OpenVZ hypervisor. Processor and Hardware underlying are not identical (corei7 or Xeon E3 in this case) so this doesnt seem to be a reason though for the different speed.


But anyway im interested on reactivating that function as it seems to really speedup relay's speed.

Thanks,
Geri





2014-03-04 0:40 GMT+01:00 Moritz Bartl <moritz@torservers.net>:
On 03/03/2014 11:53 PM, Felix wrote:
> In case there is a strong relay ie 1Gbit/s, enough cores and RAM
> so the HW is not limiting. Let's further assume only one IP.
>
> Could a single Tor daemon on Debian be a bottle neck?
> If yes, could be more performance to start two (or more) daemons and
> bind the first OR Port to :443 and the second to :8080. Both at the same
> 'eth' interface?
> Both OR Ports are based on the same IP so they would be the same family
> member.

Yes, you do want to run multiple Tor processes on a high bandwidth
machine as Tor currently does not scale well across multiple CPU cores.
You will notice that you will hit a CPU limit at ~100 Mbps (or ~300-400
Mbps with a CPU that supports AES-NI crypto acceleration).

But, currently, you can only run two Tor process per IP address.

Relays in the same /16 IPv4 subnets are considered part of one family
automatically.

--
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