To me it sounds like there isn't actually a problem. This is the way Tor
works now (now == since consensus diffs were added). It's unfortunate
that Tor isn't more multithreaded, so much happens in the same main
loop, and client throughput is momentarily impacted, but that's the way
it is and there
On 2020/05/19 15:59, William Kane wrote:
> Right after, diffs were compressed with zstd and lzma, causing the CPU
> usage to spike.
Thank you for debugging this William.
Tor behaves in the way it is designed to here. Tor uses a number of
worker threads to handle compression (and a couple of other
Hi, I'm running a non-exit relay for quite some time now and I would like to
open ports 53, 80, 443 (web ports) to be more useful.
How do you handle fraudulent complaints? What is the best approach to this
situation? Thank you for your help.
Sent with ProtonMail Secure Email.
publickey - mnlph7
