Project

General

Profile

Bug #2176

server.kbytes-per-second not working in 1.5

Added by Harry over 9 years ago. Updated about 3 years ago.

Status:
Obsolete
Priority:
Low
Assignee:
-
Category:
core
Target version:
Start date:
2010-03-22
Due date:
% Done:

0%

Estimated time:
Missing in 1.5.x:
Yes

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.

History

#1

Updated by nitrox over 9 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!

#2

Updated by Harry over 9 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.

#3

Updated by nitrox over 9 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.

#4

Updated by Harry over 9 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?

#5

Updated by icy over 9 years ago

It's a bug. The throttling code in 1.x sucks.

#6

Updated by stbuehler over 9 years ago

  • Target version set to 1.5.0
#7

Updated by gstrauss about 3 years ago

  • Missing in 1.5.x changed from No to Yes
#8

Updated by gstrauss about 3 years ago

  • Status changed from Reopened to Obsolete

Also available in: Atom