Skip to content

Performance Considerations

philipbjorge edited this page Jul 29, 2012 · 1 revision

How caching works

Infinite Social Wall makes an asynchronous call via javascript to get_stream.php?p=update everytime a user hits your social wall - code.

In most use cases, this is desired behavior. Instead of pinging your RSS feeds on a regular interval, content is loaded lazily, when it's requested. A caching mechanism inside the RSS feeder prevents feeds from being pinged more than every 15 minutes, so there generally isn't a risk of hammering your RSS provider.

When caching might not work

This might be bad in the following cases:

  • Low traffic and high social media output. If update is not being called frequently because of low traffic, you might mess social items because your RSS feed rolls over when you hit a specified number of posts (depends on the feed).
  • High traffic applications can also have a problem. If multiple users hit your page on a stale cache, your RSS feeds will be hit multiple times. Depending on how many RSS feeds your hitting and the server speed, there could be a 15 second window where multiple RSS feed requests could be made.

Solutions

Remove the asynchronous call to update and instead implement a cron job to call get_stream.php?p=update on a regular basis.

Clone this wiki locally