> On 9 Jul 2017, at 01:36, Clodo wrote:
>
>> Tor uses multithreaded crypto already: depending on the speed of your
>> processor, you can get up to 400 Mbps per instance (250 Mbps is
>> typical).
>
> Here i see a pending project:
> https://trac.torproject.org/projects/tor/ticket/1749
> and plans
On Sat, 8 Jul 2017 09:54:20 +1000
teor wrote:
> Tor uses multithreaded crypto already: depending on the speed of your
> processor, you can get up to 400 Mbps per instance (250 Mbps is
> typical).
In practice I don't remember seeing much more than 120-130% CPU use per
process, and even that, only
> Tor uses multithreaded crypto already: depending on the speed of your
> processor, you can get up to 400 Mbps per instance (250 Mbps is
> typical).
Here i see a pending project:
https://trac.torproject.org/projects/tor/ticket/1749
and plans about that:
https://trac.torproject.org/projects/tor/wi
> On 8 Jul 2017, at 08:36, nusenu wrote:
>
>
>
> Clodo:
>> The objective it's making a single Tor Relay and using on the machine
>> many daemons on a multicore server.
>> I hope someone can give me a feedback if this kind of configuration can
>> be problematic for Tor network before test in a
Clodo:
> The objective it's making a single Tor Relay and using on the machine
> many daemons on a multicore server.
> I hope someone can give me a feedback if this kind of configuration can
> be problematic for Tor network before test in a real environment.
there can only be a single tor instan
The objective it's making a single Tor Relay and using on the machine
many daemons on a multicore server.
I hope someone can give me a feedback if this kind of configuration can
be problematic for Tor network before test in a real environment.
Many Tor daemon, with X from 0..n, binded on different
