On Thu, 01 Jan 2015 23:42:42 -0500
Libertas liber...@mykolab.com wrote:
The first two account for the bulk of the calls, as they are in the
core data relaying logic.
Ultimately, the problem seems to be that the caching is very weak. At
most, only half of the calls to
From: Yawning Angel yawn...@schwanenlied.me
Subject: Re: [tor-dev] gettimeofday() Syscall Issues
On Thu, 01 Jan 2015 23:42:42 -0500
Libertas liber...@mykolab.com wrote:
The first two account for the bulk of the calls, as they are in the
core data relaying logic.
Ultimately
I would be willing to take a look at and work the clock cleanup if you guys
where able to give me some ideas on where I should start and focused on the
clean up and rewrite
Sent from my iPhone
On Jan 2, 2015, at 2:20 AM, Yawning Angel yawn...@schwanenlied.me wrote:
On Thu, 01 Jan 2015
On Fri, 2 Jan 2015 23:18:16 +1100
teor teor2...@gmail.com wrote:
IPredator has complained that tor on Linux spends too much time
calling time() when pushing 500Mbit/s, which is an issue for them
under 3.x series kernels, but not kernel 2.6.
https://ipredator.se/guide/torserver#performance
I
I also completely forgot to mention this comment:
https://trac.torproject.org/projects/tor/ticket/14056#comment:6
I'll look into doing the replacements. If anyone has concerns about
whether approx_time is exact enough, please let me know - I had never
heard of it previously. I'll look
On 01/01/2015 03:47 PM, Nick Mathewson wrote:
What part of tor is accounting for all these time/gettimeofday calls?
I set up an OpenBSD 5.6 VM and built Tor 0.2.5.10 on it. I couldn't get
chutney working because of a number of strange errors that seemed
platform-specific, so I went for a less
