Delivery-Date: Tue, 11 Aug 2015 18:42:37 -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.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	T_RP_MATCHES_RCVD 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 204771E0CA7;
	Tue, 11 Aug 2015 18:42:35 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 4799A33EF9;
	Tue, 11 Aug 2015 22:42:31 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 2610E322FD
 for <tor-talk@lists.torproject.org>; Tue, 11 Aug 2015 22:42:28 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
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 QXlEiUuqGE3i for <tor-talk@lists.torproject.org>;
 Tue, 11 Aug 2015 22:42:28 +0000 (UTC)
Received: from meiko.romanrm.net (meiko.romanrm.net [195.154.92.155])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id EAC9E20DCA
 for <tor-talk@lists.torproject.org>; Tue, 11 Aug 2015 22:42:27 +0000 (UTC)
Received: from natsu (unknown [IPv6:fd39::e9:9eff:fe8f:1bcf])
 by meiko.romanrm.net (Postfix) with SMTP id AD5AD94B8B;
 Tue, 11 Aug 2015 22:42:23 +0000 (UTC)
Date: Wed, 12 Aug 2015 03:42:23 +0500
From: Roman Mamedov <rm@romanrm.net>
To: tor-talk@lists.torproject.org
Message-ID: <20150812034223.3dff7080@natsu>
In-Reply-To: <55CA76F1.4030206@rawbw.com>
References: <CAO7N=i1fRB5cx6Z0=vLwj9_CykuPAk=NBiV=6q=FX5tD5qX2jQ@mail.gmail.com>
 <55CA76F1.4030206@rawbw.com>
X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Subject: Re: [tor-talk] (no subject)
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: multipart/mixed; boundary="===============4776224330007763088=="
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

--===============4776224330007763088==
Content-Type: multipart/signed; micalg=PGP-SHA1;
 boundary="Sig_/WlJHrI1t/tmrDQjwYPdKDS+"; protocol="application/pgp-signature"

--Sig_/WlJHrI1t/tmrDQjwYPdKDS+
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Tue, 11 Aug 2015 15:28:01 -0700
Yuri <yuri@rawbw.com> wrote:

> On 08/11/2015 15:13, Ryan Carboni wrote:
> > Why is there no multicore support for Tor? I haven't been able to find =
an
> > answer to this question.
>=20
> This is maybe because even with the quite high for the Tor network=20
> bitrates of 5-6MBps tor process never comes close to 100% CPU usage on=20
> the average hardware. So multicore capability will add no benefit.

> never comes close

> to 100% usage

> never

*Repeatedly headbangs on the desk*

Uhm so what was I talking about. Ah yes, I believe that's not the case. It
would add a great deal of benefit actually.

As to why it's not implemented, I think simply because no one has coded it =
yet.
Often things tend to not exist until someone creates them. For the reason w=
hy
it's not added, my guess is because it is rather difficult. And yeah, maybe
because other priorities, such as the need to work on other features and ke=
ep
the code reasonably simple still outweigh the performance benefit from prop=
er
multi-threading.

Currently Tor can use about 130-150% of a CPU, so if you have 4 cores you
could run 2 copies of Tor on the same IP and attain a reasonable degree of
your resources' utilization.

--=20
With respect,
Roman

--Sig_/WlJHrI1t/tmrDQjwYPdKDS+
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlXKek8ACgkQTLKSvz+PZwio7gCfcFQUQgKhjKnxObWun+RJHSKj
HMoAn1AP3ulFG0DojOTkdKGkAZPgGIGR
=aKCh
-----END PGP SIGNATURE-----

--Sig_/WlJHrI1t/tmrDQjwYPdKDS+--

--===============4776224330007763088==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============4776224330007763088==--

