Hi! Just a thought, I once measured the benefits of serving short-lived static files against dynamically generated server responses under heavy loads in a similar context. It appeared that if the server generating the response isn't able to properly cache its answers, performances degrade very fast. The easiest solution was to store the server response on disk, only once, whenever there was a change (e.g. maybe writing a plain JSON after a track change), so you can let a fast static-content webserver like Nginx, or a cache server like Varnish perform their job. Even if this file only lives for a few minutes, it can help.
-- best regards, okay_awright <okay_awright AT ddcr DOT biz> [PGP key on request] On 26/09/2011 21:43, Brandon Casci wrote: > Sorry for the delay. I'm going to post something to github today or > tomorrow. It's different than I described. A JSONP solution. Basically you > place an XSL template on the icecast server that will spit out it's now > playing info as a JSONP response. Then on your website, you have something > like jquery make a JSONP call to that url, and you can write the response to > the web page however you lilke. It's a simple solution. It might have > scaling problems if you have a lot of listeners on your now playing page at > one time, but this is probably good for most small broadcasters. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
