Ruby on Rails and the importance of being stupid

Re:Ruby on Rails and the importance of being stupid by cma on Tuesday May 19, 2009 @01:12AM (#616299)

Why should it ever be acceptable for someone to sit down in the morning to a machine with 4GB+ RAM and have things like a volume OSD take tens of painful seconds to swap in because the night before the machine ran 'updatedb' and the system decided to swap out a few bits of "unused program memory" with a useless cache of the entire disk index?

[ Parent | on HN ]

Re:Ruby on Rails and the importance of being stupid by ars on Tuesday May 19, 2009 @11:57AM (#617001)

Then set /proc/sys/vm/swappiness to 0 and be happy.

But actually linux never ejects pages to swap just for the cache. It will only eject pages for memory pressure, which, when freed, can leave extra room for cache. But it won't eject the pages in the first place for the cache.

[ Parent | on HN ]

Re:Ruby on Rails and the importance of being stupid by jimboyoungblood on Tuesday May 19, 2009 @01:52AM (#616347)

Since you know its useless, why not just turn off the updatedb cron job?

[ Parent | on HN ]

Re:Ruby on Rails and the importance of being stupid by sokoloff on Tuesday May 19, 2009 @09:19AM (#616707)

Because updatedb isn't inherently useless, but rather that file system caching (especially for pages read once) shouldn't eject application pages from RAM to disk.

Being able to run locate and have it quickly return an accurate result is useful at times. I just don't want it paging my entire session out to disk every night in order to do that.

[ Parent | on HN ]

Re:Ruby on Rails and the importance of being stupid by ars on Tuesday May 19, 2009 @11:59AM (#617007)

"I just don't want it paging my entire session out to disk every night in order to do that."

It doesn't.

[ Parent | on HN ]