I am seeing the following messages on dmesg output :-

TCP: Peer 79.211.64.145:54649/80 unexpectedly shrunk window
347253187:347272955 (repaired)
TCP: Peer 79.211.64.145:54649/80 unexpectedly shrunk window
347253187:347272955 (repaired)
TCP: Peer 79.211.64.145:54649/80 unexpectedly shrunk window
347253187:347272955 (repaired)
TCP: Peer 81.155.221.33:53075/80 unexpectedly shrunk window
1986341072:1986342532 (repaired)
TCP: Peer 81.155.221.33:53075/80 unexpectedly shrunk window
1986341072:1986342532 (repaired)
TCP: Peer 81.155.221.33:53075/80 unexpectedly shrunk window
1986341072:1986342532 (repaired)
TCP: Peer 79.211.64.145:54709/80 unexpectedly shrunk window
1128744179:1128773611 (repaired)
TCP: Peer 79.211.64.145:54709/80 unexpectedly shrunk window
1128744179:1128773611 (repaired)
TCP: Peer 79.211.64.145:54709/80 unexpectedly shrunk window
1128744179:1128773611 (repaired)
TCP: Peer 79.211.64.145:54709/80 unexpectedly shrunk window
1128744179:1128773611 (repaired)
TCP: Peer 79.211.64.145:54709/80 unexpectedly shrunk window
1128744179:1128773611 (repaired)
TCP: Peer 79.211.64.145:54709/80 unexpectedly shrunk window
1128744179:1128773611 (repaired)


If somebody can explain me ? what is that shrunk window thing?


On Thu, Jan 24, 2013 at 1:27 AM, shahzaib shahzaib <shahzaib.cb@gmail.com>wrote:

> No i didn't concerned with network operators yet. And if someone can get
> me that chinese blog for setting 2k concurrent connections using
> sysctl-settings. So far i used this guide to tune kernal.
> http://www.cyberciti.biz/faq/linux-tcp-tuning/
>
>
> On Thu, Jan 24, 2013 at 1:21 AM, shahzaib shahzaib <shahzaib.cb@gmail.com>wrote:
>
>> The load(nload) of 1500+ concurrent connections with 1Gbps port is :
>> Curr: 988.95 MBit/s
>> ##
>> ## ## ## ## ## ## ## # Avg: 510.84 MBit/s
>> ##
>> ## ## ## ## ## ## ## # Min: 0.00 Bit/s
>> ##
>> ## ## ## ## ## ## ## # Max: 1005.17 MBit/s
>> ##
>> ## ## ## ## ## ## ## # Ttl: 10017.30 GByte
>>
>> What should i see into dmesg to analyse the problem ? I'll also send you
>> the nload when the traffic will hit to its peak, at this time its average
>> traffic. The following is ifconfig eth0 output :-
>>
>> eth0 Link encap:Ethernet HWaddr X:X:X:X:X:X
>> inet addr:X.X.X.X Bcast:X.X.X.X Mask:255.255.255.192
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:3713630148 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:7281199166 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:260499010337 (242.6 GiB) TX bytes:10767156835559 (9.7
>> TiB)
>> Memory:fbe60000-fbe80000
>>
>>
>>
>> On Thu, Jan 24, 2013 at 12:29 AM, Rainer Duffner <rainer@ultra-secure.de>wrote:
>>
>>>
>>> Am 23.01.2013 um 20:03 schrieb shahzaib shahzaib <shahzaib.cb@gmail.com
>>> >:
>>>
>>> > And also the 20+ lines of vmstat are given below with 2.6.32 kernal :-
>>>
>>>
>>> There was a thread recently (well, last year sometimes) with a link to a
>>> blog in Chinese with sysctl-settings etc.
>>> It had tunings for 2k concurrent connections.
>>>
>>> Maybe somebody can dig it out?
>>> _______________________________________________
>>> nginx mailing list
>>> nginx@nginx.org
>>> http://mailman.nginx.org/mailman/listinfo/nginx
>>>
>>
>>
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx