Delivery-Date: Mon, 18 Aug 2014 07:33:41 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID
	autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id BAAD91E08C3;
	Mon, 18 Aug 2014 07:33:39 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 9BD2E30EDE;
	Mon, 18 Aug 2014 11:33:35 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 9E16C30E8F
 for <tor-talk@lists.torproject.org>; Mon, 18 Aug 2014 11:33:31 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id fke41b_GBtbl for <tor-talk@lists.torproject.org>;
 Mon, 18 Aug 2014 11:33:31 +0000 (UTC)
Received: from mail-vc0-x232.google.com (mail-vc0-x232.google.com
 [IPv6:2607:f8b0:400c:c03::232])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 77AC130A3A
 for <tor-talk@lists.torproject.org>; Mon, 18 Aug 2014 11:33:31 +0000 (UTC)
Received: by mail-vc0-f178.google.com with SMTP id la4so5663812vcb.9
 for <tor-talk@lists.torproject.org>; Mon, 18 Aug 2014 04:33:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=YS7tYV4V9EiQGa7Nb2olALv4wo2zMAwy2mch2YLmqJ0=;
 b=BcCYqxnP/P/F1jon7AIJjrLt5yMPMKXzcNQ/Tfoy8Wt5Wbt2GTQhxoyFZqNSJcmdvg
 uzu5GoRjGDVeyeVTziefh1HTfYMJuRKIs4kH09lyp3Y+aGazlaUHmGiYP2MHkdb/KMfo
 GmoqZjCKyWhGWGFrEQeiTk5cUKK8FUYsYl5vfmWRmmOQRAodoxE+s/vZ4xwZl3O2Vost
 U3UyI8P40bTeEpVyFndfxjT1FpsXThBCZjsGGnbqZQVcmBc9LF+74nT7Wza+eDFU2n7V
 HRaoagag+Bo9xrmS7oUhWTRFccROtDGB9F/mO33ZpeCKVr0lvfcC/EmqPBMAWW1PzrOK
 z8Lw==
MIME-Version: 1.0
X-Received: by 10.220.2.136 with SMTP id 8mr24638899vcj.17.1408361608947; Mon,
 18 Aug 2014 04:33:28 -0700 (PDT)
Received: by 10.220.104.201 with HTTP; Mon, 18 Aug 2014 04:33:28 -0700 (PDT)
In-Reply-To: <7946984e.09b9a8bc@fabiankeil.de>
References: <CAHXoDSAM=D1kvodauWYkZ9+9UPFtuFfKKqgeRAv=qJS1D9V5iA@mail.gmail.com>
 <53EBC80F.6040405@gmx.com> <20140813210532.GN8819@moria.seul.org>
 <7946984e.09b9a8bc@fabiankeil.de>
Date: Mon, 18 Aug 2014 13:33:28 +0200
Message-ID: <CAHXoDSDPkorgY6t-0TtEn1DsRx2C4mLpouP9WrwL0ocEVaQHCw@mail.gmail.com>
From: Martin S <shieldfire@gmail.com>
To: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] Performance
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

Considering the responses in this thread, I am now testing the Tor BB.
However the startup time for this is monstruous. Running through the
initial setup routine, the thing just seems to hang on connecting to
Tor network. What could be wrong?

2014-08-16 15:23 GMT+02:00 Fabian Keil <freebsd-listen@fabiankeil.de>:
> Roger Dingledine <arma@mit.edu> wrote:
>
>> On Wed, Aug 13, 2014 at 03:18:23PM -0500, Joe Btfsplk wrote:
>> > The Privoxy part of the chain could be an issue.  What is your
>> > reason for using Privoxy?
>> > In general, I find Tor to be faster overall, since overhauls in
>> > TorBrowser - when they stopped using Privoxy (& likely started other
>> > speed increasing methods).
>> > Other network changes could be partly responsibility for increased
>> > speed.
>>
>> Privoxy will be slower for two reasons:
>>
>> A) It doesn't do the pipelining, etc that your browser can do. Earlier
>> versions of privoxy would fetch the whole page before passing any of
>> it to the browser. Maybe newer versions of Privoxy are smarter, but I
>> bet there are still web performance features that it disables by adding
>> another link in the chain.
>
> Privoxy has to buffer the whole page if it's configured to filter it
> as the last byte might affect whether or not the first byte has to
> be modified.
>
> If filtering is disabled (globally or for the current response),
> the page isn't buffered. Encrypted responses aren't buffered either.
> Earlier versions of Privoxy behaved the same way and I believe even
> Privoxy's predecessor was "smart" enough for this.
>
>> B) It doesn't make use of Tor's "optimistic data" feature, which sends
>> the first chunk of application-level data along with the begin cell,
>> effectively cutting out one of the two round-trips for a new page fetch.
>
> Privoxy 3.0.21 and later support Tor's "optimistic data" feature
> (with some limitations). While it technically improves performance,
> it's seems rather hard for a human to tell whether or not it's enabled,
> though.
>
>> I guess the broader question is what the original poster was trying
>> to do -- if the goal is to give Tor's protection to everybody in the
>> organization, and the way they did it was to leave everybody using
>> Internet Explorer, and then redirect outgoing traffic into Privoxy
>> which sends it through Tor, then the users are missing out on all
>> the application-level privacy and security features that Tor Browser
>> gives you:
>> https://www.torproject.org/projects/torbrowser/design/
>
> No arguments there.
>
> Whether or not they are missing out on "performance" and which
> part of the chain is to blame is a different question, though.
>
> Fabian
>
> --
> tor-talk mailing list - tor-talk@lists.torproject.org
> To unsubscribe or change other settings go to
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
>



-- 
Regards,

Martin S
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

