I think I have fixed the live stream issue from last week or at least I I have changed the live stream issue

From last week

So last week in the middle to show the live stream cut out and the reason why it had

Consumed something like seven or eight gigs of RAM and the server has eight and so it got killed for the out of memory killer

And they restarted it and almost everyone was able to rejoin and it didn't use nearly as much ram as it did before

So it sounds kind of like a memory leak

And it didn't seem related to the number of listeners directly necessarily now when I built the new website I added this

Listen or count thing that was like the the page

Peer out of the just does an a-jacks request batch the server the server checks with the I can the ice cast server

Which ones this like private admin interface

And gives us XML file back and the server my server parses it and feeds it back through the to the user and updates the page

Anyway, my theory is that that like check the status request because it was being checked every like 15 seconds

By every listener on the stream if there's any leak in that

That was a pretty aggressive amount of checking and so that might have resulted in it

Now over the course of that like the second part of the show after it was killed and restarted

It still got all the way up to about 1.7 gigs of RAM

Where it stayed until a half hour ago so it stayed there all week with no listeners

Until a half hour ago when I restarted it so we'll see how it goes so far right now we are at a

Little under let's see we're at a little under 800 megs

That sounds high to me so maybe this isn't solved

But we'll see if it continues to grow anyway the fix that I did was I implemented caching on that status value so that now

My server is caching the results gets from the ice cast server for about 30 seconds

...