Project

General

Profile

Actions

Bug #355

closed

Traffic shaping == traffing stalling

Added by Anonymous over 19 years ago. Updated almost 17 years ago.

Status:
Fixed
Priority:
Normal
Category:
core
Target version:
-
ASK QUESTIONS IN Forums:

Description

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:

-- sixer


Files

strace.txt (29.6 KB) strace.txt strace output -- sixer Anonymous, 2005-11-06 15:15
Actions #1

Updated by jan over 19 years ago

  • Status changed from New to Assigned

please add strace output as file.

Actions #2

Updated by Anonymous over 19 years ago

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.

-- cliff

Actions #3

Updated by Anonymous over 19 years ago

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 host:2096 ESTABLISHED

tcp 0 8484 xbox:www host:2088 ESTABLISHED

tcp 0 12726 xbox:www host:2097 ESTABLISHED

tcp 0 11312 xbox:www host:2098 ESTABLISHED

tcp 0 11312 xbox:www host:2090 ESTABLISHED

tcp 0 8484 xbox:www host:2091 ESTABLISHED

tcp 0 11312 xbox:www host:2100 ESTABLISHED

tcp 0 14140 xbox:www host:2092 ESTABLISHED

tcp 0 12726 xbox:www host:2085 ESTABLISHED

tcp 0 11312 xbox:www host:2093 ESTABLISHED

tcp 0 14140 xbox:www host:2102 ESTABLISHED

tcp 0 8484 xbox:www host:2086 ESTABLISHED

tcp 0 12726 xbox:www host:2094 ESTABLISHED

tcp 0 12726 xbox:www host:2118 ESTABLISHED

tcp 0 14140 xbox:www host:2103 ESTABLISHED

tcp 0 12726 xbox:www host:2087 ESTABLISHED

tcp 0 16968 xbox:www host:2095 ESTABLISHED

tcp 0 11312 xbox:www host:2127 ESTABLISHED

The opposite host appears to be using a download accelerator.

-- sixer

Actions #4

Updated by stbuehler almost 17 years ago

  • Status changed from Assigned to Fixed
  • Resolution set to fixed

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).

Actions

Also available in: Atom