Caching Woes

An year ago, around this time, I started working on feedmug.com – an RSS feeds reader that aims to provide the best reading experience. After 6 months of development and using, feedmug.com was launched in March 2011.

  https://pjps.wordpress.com/2011/03/15/introducing-feedmug-com

Since then, slowly but steadily, it has been growing good. Recently feedmug hit its first roadblock when the hosting provider stopped its back-end caching server saying, “excessive resource usage on a shared hosting“.

The thing is, feedmug has a list of RSS feeds for which it maintains the local cache. User requests are served from this local cache so that the response time is minimum. The cache needs to be kept updated all the time, which is done by the caching server.

I’m working on replacing the current caching server with a new one, which should consume minimum system resources. Hope it all works out well.

Till then, feedmug won’t be able to display the updates count next to your feeds. But if you click on the feed, it’ll always fetch the latest posts and news for you.

I’m extremely sorry for this inconvenience. 😦

Advertisements

2 thoughts on “Caching Woes

    1. I’m currently using DreamHost. I looked at Hetzner’s plans as well, but let’s see, I’m keeping that as the last resort.

      Thanks! 🙂

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s