On May 10, 3:42 pm, Antoni <antonimassom...@gmail.com> wrote:
> It seems mod_bw was eating up my system resources somehow. Has anyone
> tested mod_bw or any other bandwidth limiter module for Apache 2?
>
> Thanks

yeah I've been using mod_bw since august last year on apache 2.2.x
(win32) with no issues.
Here's an excerpt from a vhost config

BandWidthModule On
AddOutputFilterByType MOD_BW audio/mpeg audio/x-mpeg audio/x-mpeg-3
audio/mpeg3
BandWidth all 10240
MinBandWidth all -1
#consider how best to serve this error
BandWidthError 510
ErrorDocument 510 /error/HTTP_SERVICE_UNAVAILABLE.html.var

this just reduces the rate at which mp3's are served from the vhost.

Are you sure it wasn't a connection throttle rather than bandwidth, I
got the feeling that your bw was fine when I was eventually able to
connect, that it was initial latency rather than bw.
Could it have been the case that as mod_bw buffered content for many
users, you hit the RAM limit and started using virtual RAM? When
serving films round the home, the memory usage for the apache child
does oscillate by a few MB which wouldn't happen if you decided to use
shaper to shape your traffic from the server, you would have the added
advantage of having hard and soft limits with shaper (linux)