Am Mon, 19 Dec 2011 16:32:19 -0800
schrieb Mike Perry mikepe...@torproject.org:
Hi,
Just to be sure, I decided to shut off the experiment on Sunday at 3pm
US Pacific time anyways. It looks like the performance has in fact
gotten worse since then.
Does this mean the feedback was definitely
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/15/2011 3:43 PM, Mike Perry wrote:
I've made the following changes this afternoon:
1. On the assumption that we're seeing the huge increase in
variance on torperf because faster nodes are only *sometimes* at
max capacity, but most of the
Hi Mike,
Around the 24 of November the performance graph reported a value below
4 sec. per 50kb, and right now including the last few days we can
barely reach 6 sec. per 50kb.
Or in other words, we lost way more than 50 % peformance since that
day. Unless you guys are about to really step up the
Thus spake Sebastian Urbach (sebast...@urbach.org):
Around the 24 of November the performance graph reported a value below
4 sec. per 50kb, and right now including the last few days we can
barely reach 6 sec. per 50kb.
Or in other words, we lost way more than 50 % peformance since that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/13/2011 10:34 PM, Mike Perry wrote:
Thus spake Tim Wilde (twi...@cymru.com):
We're not seeing source port exhaustion, but we are seeing two
warns, one of which I haven't been able to nail down:
2011 Dec 13 20:22:07.000|[notice] We
On Mon, Dec 12, 2011 at 6:52 PM, Mike Perry mikepe...@torproject.org wrote:
Thus spake Jon (torance...@gmail.com):
In adding further info on the topic, I have noticed and looked back
over the past couple of weeks and have seen a drop of of usage of
about 43% s of today. I am not in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/12/2011 9:14 PM, Mike Perry wrote:
It looks like Moritz is seeing some evidence of TCP sourceport
exhaustion in his Tor logs: [warn] Error binding network socket:
Address already in use.
He's also monitoring TCP connection counts on each
Thus spake Tim Wilde (twi...@cymru.com):
We're not seeing source port exhaustion, but we are seeing two warns,
one of which I haven't been able to nail down:
2011 Dec 13 20:22:07.000|[notice] We stalled too much while trying to
write 8542 bytes to address [scrubbed]. If this happens a lot,
In adding further info on the topic, I have noticed and looked back
over the past couple of weeks and have seen a drop of of usage of
about 43% s of today. I am not in the higher bracket as others, but I
have been in the 3 bars bracket only up till recently.
Don't know if this will help, but if
On 12.12.2011 20:18, Tim Wilde wrote:
Any specific tips on how you're pushing 700Mbps from a single instance
(I assume that's what that's indicating) beyond what's on your wiki?
With AES-NI and most (maybe all) of the tweaks I've found on your
pages (awesome resource, by the way, thanks for
Thus spake Tim Wilde (twi...@cymru.com):
I try to keep everything I do documented on that wiki. All these
servers run four instances of Tor each (one per core) and traffic
is accounted for in total. Also, keep in mind that vnstat counts
both incoming and outgoing traffic, so 700Mbps in
Over Thanksgiving and into early this week, we ran an experiment to
test a feedback mechanism to attempt to allocate usage of the Tor
network such that the measured stream capacities through all relays
became equal:
12 matches
Mail list logo
