[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Let's talk about HTTPS Everywhere



On Tue, 25 Jan 2011 07:58:28 +0100
Jochen Schulz <ml@well-adjusted.de> wrote:

> Celejar:
> > On Mon, 24 Jan 2011 22:33:28 +0100
> > Jochen Schulz <ml@well-adjusted.de> wrote:
> > 
> >> Celejar:
> >>> 
> >>> I understand that you're technically adding traffic and processor
> >>> overhead; the question is how much?
> >> 
> >> My 1.66GHz atom D510 can encrypt/decrypt AES with ~20MByte/s on a single
> >> core. Typically, my wifi reaches only 10% of that throughput.
> >> Additionally, encryption is usually done by the network adapter in
> >> hardware, as far as I know. The host CPU shouldn't be stressed by that.
> > 
> > Thanks. What's the CPU usage like while doing AES on 20Mb?
> 
> A single core get's used 100% by the kworker thread. But actually it's
> not 20MB/s, but 25MB/s while reading (decrypting) and 35MB/s while
> writing (encrypting). I just tested it again.

So does that mean that your wireless throughput with encryption enabled
is CPU-bound, and that you'd be getting better throughput with a more
powerful CPU (or without encryption)?

Celejar
-- 
foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


Reply to: