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
Which is not the case since OGG/MP3 can requested individualy.
> a local streaming server (icecast2) and provide them with a link to the
> local source...
But this mean, you
On Mon, Feb 11, 2008, Michelle Konzack wrote:
> 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...
Then you should look at why your operating system disk caching
> On Mon, Feb 11, 2008, Michelle Konzack wrote:
> > 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...
On 13.02.08 09:55, Adrian Chadd wrote:
> Then you should
> 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 r
On Wed, Feb 13, 2008, Matus UHLAR - fantomas wrote:
> maybe the data are never fetched from disk, always from remote server and
> just always stored to the cache (to be never fetched from there).
>
> Or maybe the squid memory usage is too big and machine swaps...
Bit hard to say without access t
Matus UHLAR - fantomas wrote:
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
