I really like Tracks, it’s an awesome app. But on my baby VPS (which has 256mb of RAM), it uses about 90 of those megs. Is that normal? Is there anyway I can pair down that amount? As it is, I need to figure out how I can keep Tracks going without affecting my main site. Which might be upgrade my VPS

I am using Apache 2.2 with Phusion Passenger and MySQL. I’ve got PassengerPoolIdleTime set to 0 (ie, keep the rails processes alive indefinitely). Tracks, version 1.7, is running in production mode.

I have this stack running too.
passenger-memory-stats reports “Total private dirty RSS: 87.99 MB” after rendering the home page (52MB is related to my tracks instance)

I’m afraid this is because of ror. I don’t think we can trim down tracks much to significantly reduce the memory footprint. But I’m open to suggestions

A suggestion might be to run tracks on mongrel/webbrick and use a reverse proxy of apache to connect to it. It saves the memory that passenger uses (~35MB), but is a somewhat less flexible setup. Make sure to let apache handle the static content, i.e. /public