Ticket #355 (closed defect: fixed)

Opened 3 years ago

Last modified 1 week ago

Traffic shaping == traffing stalling

Reported by: sixer@psycholicious.net Assigned to: jan
Priority: normal Milestone:
Component: core Version:
Severity: normal Keywords:
Cc: Blocking:
Need Feedback: 0

Description (Last modified by jan)

When server.kbytes-per-second is set in lighttpd 1.4.7 and earlier, transfers stop to a halt early in the proces. The amount of kbytes at which the transfer stops, is variable. I've had values between 13 KB and 144 KB.

When server.kbytes-per-second is unset, no problems occur.

strace output while performing a test download which stalls:

Attachments

.2 (0 bytes) - added by sixer@psycholicious.net on 11/06/2005 03:15:18 PM.
strace output
strace.txt (29.6 kB) - added by sixer@psycholicious.net on 11/06/2005 03:15:32 PM.
strace output

Change History

11/06/2005 03:08:35 PM changed by jan

  • status changed from new to assigned.
  • description changed.

please add strace output as file.

11/06/2005 03:15:18 PM changed by sixer@psycholicious.net

  • attachment .2 added.

strace output

11/06/2005 03:15:32 PM changed by sixer@psycholicious.net

  • attachment strace.txt added.

strace output

12/25/2005 12:42:27 AM changed by cliff@develix.com

I've been using traffic shaping in 1.4.7 successfully with values ranging from 16K to 128K on some moderately loaded sites (~50GB/month, lots of images, videos) and haven't seen any issues. Haven't tried it earlier than 1.4.7.

That being said, I have seen issues like this with a faulty NIC. NIC worked fine 99.9% of the time, but would mysteriously stall when using apt/yum. File size seemed to make no difference. Interestingly it was almost always the same files. It wasn't the remote server because I could use a different system to download the files from the same place without issue. Finally replaced the NIC and problem disappeared.

01/02/2006 09:20:32 PM changed by sixer@psycholicious.net

Strangely enough, now, under 1.4.8, downloads exceed the maximum kilobytes per second, at least according to a netstat -a:

While server.kbytes-per-second is set to 80:

Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 16968 xbox:www [remote host]:2096 ESTABLISHED
tcp 0 8484 xbox:www [remote host]:2088 ESTABLISHED
tcp 0 12726 xbox:www [remote host]:2097 ESTABLISHED
tcp 0 11312 xbox:www [remote host]:2098 ESTABLISHED
tcp 0 11312 xbox:www [remote host]:2090 ESTABLISHED
tcp 0 8484 xbox:www [remote host]:2091 ESTABLISHED
tcp 0 11312 xbox:www [remote host]:2100 ESTABLISHED
tcp 0 14140 xbox:www [remote host]:2092 ESTABLISHED
tcp 0 12726 xbox:www [remote host]:2085 ESTABLISHED
tcp 0 11312 xbox:www [remote host]:2093 ESTABLISHED
tcp 0 14140 xbox:www [remote host]:2102 ESTABLISHED
tcp 0 8484 xbox:www [remote host]:2086 ESTABLISHED
tcp 0 12726 xbox:www [remote host]:2094 ESTABLISHED
tcp 0 12726 xbox:www [remote host]:2118 ESTABLISHED
tcp 0 14140 xbox:www [remote host]:2103 ESTABLISHED
tcp 0 12726 xbox:www [remote host]:2087 ESTABLISHED
tcp 0 16968 xbox:www [remote host]:2095 ESTABLISHED
tcp 0 11312 xbox:www [remote host]:2127 ESTABLISHED

The opposite host appears to be using a download accelerator.

05/06/2008 09:43:48 AM changed by stbuehler

  • status changed from assigned to closed.
  • resolution set to fixed.
  • blocking changed.
  • pending changed.

The server.kbytes-per-second limit is not that precise; for example on my system lighty send 64kb in one block (so it would send 2 blocks per second till it realizes it is over the limit).

Add/Change #355 (Traffic shaping == traffing stalling)




Change Properties
Action