From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Thu, 7 May 2015 06:17:36 -0700 To: 9fans@9fans.net Message-ID: In-Reply-To: References: <87C61423-7C13-4516-88B5-C2ABA7D32AA9@me.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] fossil+venti performance question Topicbox-Message-UUID: 501a80d8-ead9-11e9-9d60-3106f5b1d025 > cpu% cat /net/tcp/3/local > 127.0.0.1!57796 > cpu% cat /net/tcp/3/remote > 127.0.0.1!17034 > cpu% cat /net/tcp/3/status > Established qin 0 qout 0 rq 0.0 srtt 80 mdev 40 sst 1048560 cwin > 258192 swin 1048560>>4 rwin 1048560>>4 qscale 4 timer.start 10 > timer.count 10 rerecv 0 katimer.start 2400 katimer.count 427 hmm... large rtt, which suggests that someone is not servicing the queues fast enough. this is for the 1gbe machine in the room with me 11/status:Established qin 0 qout 0 rq 0.0 srtt 0 mdev 0 sst 2920 cwin 61390 swin 1048560>>4 rwin 1048560>>4 qscale 4 timer.start 10 timer.count 10 rerecv 0 katimer.start 2400 katimer.count 2101 i would suggest turning on netlog for tcp while booting and caputing the output. sorry for the short investigation. gotta run. - erik