Re: [squid-users] Re: Re: Re: Cache for mp3 and ogg in memory...

> Am 2008-02-10 08:47:14, schrieb Joel Jaeggli:
> > If you have more than one listener for the same stream, you relay it to

On 11.02.08 01:01, Michelle Konzack wrote:
> Which is not the case since OGG/MP3 can requested individualy.

by using the same URI? or by different URI each time a song is requested?
each of this makes problems with HTTP caching...

> > a local streaming server (icecast2) and provide them with a link to the
> > local source...
>
> But this mean, you have realy heavy Disk-IO. and imagine, you have only
> 4 peoples/clients which hear different OGG/MP3 the Read-head will stand
> never still and will never read sequetaly.

4 users listening to 160 kbit/s songs in parallel will make ... 640 kbit/s
traffic. most of disks can handle that :) Of course if squid is configured
to fetch more data than user requests (see quick_abort settings) and users
tend to switch songs fast, it may make problems.

> This kill all harddrives... And Yes, I can could use SCSI-Drives but
> a Raid-5 of at least 3 drives plus Hotfix and a controller would cost
> arround 5000 Euro. Nearly 16 times the price of the computer itself.

do never use raid-5 for things like squid cache. Better no raid - use single
drives, with one cache_dir on each.

> > If they're all listing to different remote sources at different times
> > then there's no point in caching it...
>
> But if I read the logs, they are around 150-180 files which are heared
> all the time and they have in summary arround 800 MByte. So creating a
> Ram-Cache of 1 GByte would do wonder...

I still have no idea what URIs are requested by users when they are
listening to those songs. In such case I can't do anything but guess...

-- 
Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Linux is like a teepee: no Windows, no Gates and an apache inside...