>
> Every hour, Tor downloads directory documents, creates diffs to recent
> consensuses,
> and compresses the documents (and diffs) using gzip, zstd, and lzma.
>
>
Thanks for getting back to me.
Except during the mentioned peaks, the relay only uses 5 - 6 % of available
CPU power on a machine tha
>If you have the CPU, RAM, and disk space, you should leave these settings on.
>
>It will affect some client versions' choice of guards:
>https://trac.torproject.org/projects/tor/ticket/24312#comment:4
I have guards that are bottle-necked by CPU, and I'm still exploring various
options in respo
On 6 Feb 2018, at 06:13, tor wrote:
>> If anyone wants to disable directory document caching, they can set:
>> DirPort 0
>> DirCache 0
>
> This results in the following log entry:
>
> [warn] DirCache is disabled and we are configured as a relay. This may
> disqualify us from becoming a guar
> If anyone wants to disable directory document caching, they can set:
> DirPort 0
> DirCache 0
This results in the following log entry:
[warn] DirCache is disabled and we are configured as a relay. This may
disqualify us from becoming a guard in the future.
That's a bit vague. What's that
> On 5 Feb 2018, at 23:21, Gary Smith wrote:
>
> Hi,
>
> I have noticed that after a few minutes of becoming online, and randomly
> perhaps a couple of times every hour (??) tor uses 100 % processor on all
> cores for about 40/50 seconds.
>
> I am curious what is tor doing internally to need
Hi,
I have noticed that after a few minutes of becoming online, and randomly
perhaps a couple of times every hour (??) tor uses 100 % processor on all
cores for about 40/50 seconds.
I am curious what is tor doing internally to need so much power? There is
normally isn't more than 4 mbits going th
