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

Re: On the performance scalability of Tor

To: or-talk@xxxxxxxxxxxxx
Subject: Re: On the performance scalability of Tor
From: "Michael_google gmail_Gersten" <keybounce@xxxxxxxxx>
Date: Wed, 18 Jul 2007 21:43:06 -0700
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-talk-outgoing@xxxxxxxx
Delivered-to: or-talk@xxxxxxxx
Delivery-date: Thu, 19 Jul 2007 00:43:15 -0400
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GDQXHbagBMHORl+zVS7gAgo1ChFWuVtppgzr6qXBwv5HphWU2MtN/ZJTdidXOV8yfSMuLG7YpZScNw/pBDwx8oAtqPT3m5pp8HrMMrfKrTWSGXfD3jhkfg8yevVXQqssutAbj2klhLqx7sFQLepk9FHsGyk7h+ZmMXX+OFPcwfA=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=TBRBT7EkaxttCehOaza+ParoiO1sqztbP9LrMY76xnGO6lrDUZUW3YrNNIc3+HXMTBReWiD4vrsNiv7sbqUI2B+NF0czjnr1gzyZUX2/RVwSlSlFkSKPswjm1JrpiGiGC+w9K2ydxIQjxyV3kWhdicVUOBFF7beCyyvya9NfjWE=
In-reply-to: <20070719033554.GX11269@xxxxxxxxxxxxxx>
References: <20070718145816.GX4473@xxxxxxxxxxxxxxxxx> <200707190025.30186.robert@xxxxxxxxxxxxxxx> <20070719024334.GA1226@xxxxxxxxxx> <20070719025214.GB1226@xxxxxxxxxx> <20070719033554.GX11269@xxxxxxxxxxxxxx>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx

They can be issued concurrently. Tor doesn't care.


Indeed; I will see vidalia show a lot of connectings all at once,
followed by all switching to open at once (TCP streams inside a tor
circuit).

The overhead to open a new TCP HTTP connection through a tor circuit
seems to be very long. I know it has to be encrypted/decrypted at each
node, as well as originated at the exit to the destination, but I have
to wonder: Can this be sped up at all?

The discussion about fast nodes: Is there a way to tell the client,
"Only select fast nodes"? Does "fast" imply high throughput (but it
might be slow to start up), or fast startup/turn around?

Follow-Ups:
- Re: On the performance scalability of Tor
  - From: Vlad \"SATtva\" Miller

References:
- On the performance scalability of Tor
  - From: Steven Murdoch
- Re: On the performance scalability of Tor
  - From: Robert Hogan
- Re: On the performance scalability of Tor
  - From: Mike Perry
- Re: On the performance scalability of Tor
  - From: Mike Perry
- Re: On the performance scalability of Tor
  - From: Roger Dingledine

Prev by Author: Re: What happens when I shut down my Tor-server?
Next by Author: Re: Tor takes too much RAM
Previous by thread: Re: On the performance scalability of Tor
Next by thread: Re: On the performance scalability of Tor
Index(es):
- Author
- Thread