[Mongrel] Debugging high CPU with Mongrel
dallas.devries at gmail.com
Thu Dec 7 09:30:44 EST 2006
Hi guys thanks for the response,
Yeah I initially figured that the # of files in the directory was the
problem and it was the first thing I changed earlier this week. I changed
my caching to use many more subdirectories so that I don't have 10,000+
files in one directory any more. Right now my largest directory has about
2000-3000 files most the rest are much smaller than this. Unfortunately that
change did not help the problem...I can have upwards of 50,000 files so I'm
not sure how feasible memcached is at the moment. Anyways I'm almost done
with a clean install with apache/mongrel cluster mentioned by Konstantin so
hopefully that solves my problem.
On 12/6/06, anjan bacchu <anjan.summit at gmail.com> wrote:
> directory. When you reach 10-100K files in a single directory you
> > may notice the slowdown without a stopwatch. NetApp's own file
> > system was designed to have a constant access time regardless of the
> > number of files in the directory (that was their claim to fame anyway).
> > Bottom line is that I wouldn't assume that a directory with 10K+
> > files is not the main reason for your performance degradation.
> > Hope this helps,
> > Konstantin
> Hi Konstantin,
> You're right on.
> Dallas : ReiserFS is designed to perform well in such a situation of
> having a lot of small files in the same directory. Can you switch to
> ReiserFS ? If not, can you switch to memcached ? Are you expiring your
> sessions ?
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mongrel-users