Bug #2176
closedserver.kbytes-per-second not working in 1.5
Description
Yeah, I know 1.5 isn't supported.. I just wanted to through out this possible bug in it.
I have server.kbytes-per-second = 50 in my config; I can easily hit 400 KB/s off a non-local connection, even though I set that constant and killed and reran lighttpd.
Updated by nitrox almost 15 years ago
- Status changed from New to Missing Feedback
Do you still use server.max-worker != 1 ? If so, sorry, no further support. Read the hints on the wiki!
Updated by Harry almost 15 years ago
- Status changed from Missing Feedback to Reopened
No, I am not specifying the worker count (so it's 1, I assume).
server.kbytes-per-second = 50
##server.max-worker = 1
Is the only parts in my config relating to this. workers is commented out.
Updated by nitrox almost 15 years ago
I meant "Need Feedback" last time, sorry for that.
Server.kbytes-per-second is not that reliable, some connections might not get the attention they deserve but that shouldn´t result in more bandwidth than specified. On the other hand i get results within the range of 100-260 kbytes/s on my server if i set it to 50, this isn´t as exact as you might want it, but a good start.
Outgoing can always be limited very fine-grained via iptables, incoming is a little more tricky.
Updated by Harry almost 15 years ago
Server.kbytes-per-second is not that reliable
So its this a bug, or just a error-by-design?
Outgoing can always be limited very fine-grained via iptables
Is there any guides on this?
Updated by icy almost 15 years ago
It's a bug. The throttling code in 1.x sucks.
Also available in: Atom