[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Windows buffer problems
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: Windows buffer problems
- From: Lee <ler762@xxxxxxxxx>
- Date: Fri, 19 Dec 2008 10:54:58 -0500
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Fri, 19 Dec 2008 10:55:05 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=RKl5oMXZwR7Q0Kq1hkAGUq1aVKORXAe2hLf+jhsBCf0=; b=gMXbTQnbmjkNNbFEwGrjlCvnUNzVgtTp2J/cBxQ2yh+ZaWNtndI6inio9wzvvFJtXJ RFbYYfaGRWxiHRGGUpB0ohk8ERcvmGBL6jqLTWvEk8M7d6RvI9plIQQPx87piN4k4wso ygobvlOreK6N/PRfzwbLU+E5zLG21g40fvve0=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=x/M5ATjMmipd5mev+2g93GMaIE9whJsk/7Pv0fkMNs2Ikpa3l7mVTs7R5JDD6zuUto oFqkVae7n43YZVGVxmfa1wm18RGlvLsR74dbDBudYp6cuF3y2JSYCu3YJ+CR75ofAdnT z/zfpUg15V7TMcziPwwpHcKtbE1U7/VW153eA=
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
On 12/19/08, coderman <coderman@xxxxxxxxx> wrote:
>
> there are actually two issues (or more?) for non-server Windows
> running Tor. the usual problem Tor encounters is not related to the
> number of concurrent attempts but to kernel non-paged memory resources
> consumed to exhaustion when lots of active non-overlapped-I/O sockets
> are in use. details here:
> https://wiki.torproject.org/noreply/TheOnionRouter/WindowsBufferProblems
This bit from the web page:
"Manipulating
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\GlobalMaxTcpWindowSize
and TcpWindowSize to 0xfaf00 (1027840) seemed to increase the time to
failure when running Tor and BitTorrent."
seems backwards. Instead of buffering up to 16KB of data for each
open connection you're telling the system to buffer up to 1MB of data
for each open connection. How can increasing system buffer usage help
if the problem is insufficient buffer space?
So I'm wondering if the problem could be that the system runs out of
available ports.
XP defaults to using something like 4K ports and 240 seconds for
keeping a closed socket in the timed wait state. Has anyone tried
bumping the allowable port numbers up to 64K and dropped the timed
wait state time to 16 seconds?
----
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
"MaxUserPort"=dword:0000fffe
"TcpTimedWaitDelay"=dword:00000010
"StrictTimeWaitSeqCheck"=dword:00000001
----
Lee