4 ms·
Vimcasts.org runs on Radiant CMS, which has page caching enabled by default. My problem was too many app instances spinning up. I've limited the PassengerMaxPoo
by nelstrom 17y ago
Vimcasts.org runs on Radiant CMS, which has page caching enabled by default. My problem was too many app instances spinning up. I've limited the PassengerMaxPoolSize and PassengerMaxInstancesPerApp both to 2, which seems to have fixed it.
I appreciate this burst of traffic to help me get to the bottom of this.
- sohooo 17y agoI wonder why you're running a clean site like vimcasts.org on a full-blown CMS. Imho this scenario longs for simpler solutions. Static site generators - in the Ruby universe: toto, nanoc, webby - come to mind.
- rmoriz 17y agoWell, I guess your passenger/apache is not configured right to deliver the generated static files without using ruby or passenger besides your MaxInstances/PoolSize options. I remember some issues with passengers and page caching (on nginx e.g.) which needed some tweaks.
- rufo 17y agoRadiant uses Rack::Cache behind the scenes, so it still needs to be running. I'm sure there's some reason it doesn't use Rails static caching, but even having used Radiant I'm not sure what it would be...