[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: aes performance

To: or-talk@xxxxxxxxxxxxx
Subject: Re: aes performance
From: Olaf Selke <olaf.selke@xxxxxxxxxxxx>
Date: Mon, 23 Feb 2009 18:45:24 +0100
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-talk-outgoing@xxxxxxxx
Delivered-to: or-talk@xxxxxxxx
Delivery-date: Mon, 23 Feb 2009 12:45:53 -0500
In-reply-to: <e646fda30902230833y6fa21035wc4c38317b7c23137@xxxxxxxxxxxxxx>
References: <49A158AB.2090703@xxxxxxxxxxxx> <49A2CD79.8030602@xxxxxxxxxxxxxxxxxxxxxx> <e646fda30902230833y6fa21035wc4c38317b7c23137@xxxxxxxxxxxxxx>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.19 (Windows/20081209)

John Brooks schrieb:
> 
> All of that aside, the encryption speed is a non-issue here. Unless
> you're using a large portion of a gigabit connection, AES will work far
> faster than your line speed on a modern processor.

it depends :-) I supposed cpu encryption speed being the limiting factor
for the majority of the top 20 nodes:
http://trunk.torstatus.kgprog.com/index.php?SR=Bandwidth&SO=Desc

With aes-128 and 16 byte blocks my node would be limited to 42 MBit/s
even if all cpu time would be spend within aes crypto, which isn't very
realistic.

Olaf

References:
- aes performance
  - From: Olaf Selke
- Re: aes performance
  - From: Arjan
- Re: aes performance
  - From: John Brooks

Prev by Author: Re: aes performance
Next by Author: Re: aes performance
Previous by thread: Re: aes performance
Next by thread: Re: aes performance
Index(es):
- Author
- Thread