Basically what I'm trying to achieve is:
mp3 files > 1MB downloaded are forced to a slower speed.
mp3 files < 1MB are downloaded without restriction.
So, here's my delay pool stanza:
acl magic_mpeg url_regex -i .mp3 .mpeg .mpa ....etc
delay_pools 1
delay_class 1 1
delay_parameters 1 131072/1045876 # - ie. 128k/1MB
delay access 1 allow magic_mpeg
delay access 1 deny all
Download one x 2.5MB mp3 file - works fine - burst rate up to 1MB
and then downloads at 128k.
Download two x 2.5MB mp3 file (different names!) - first one has burst
rate up to 1MB, then starts at 128k; 2nd one *does not* download at
the burst rate, but starts off at a slower rate. This is not what I
want.
So, I tried with a Class 2 delaypool. With
delay_parameters 1 262144/1048576 131072/1048576
This works *reasonably* well with up to 3 parallel downloads - ie. each
session does seem to get a burst rate up to the 1MB size. However, I'm
wondering
how scalable this is? ie. say I have 200 parallel downloads from 200
different IP's
- will each one get the burst rate for their IP bucket or are they all
sucking from
the global bucket too?
thanks,
Mike
Received on Tue Jul 31 2001 - 08:34:13 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:01:21 MST