[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Running a repository out of RAM?

From: Troy Curtis Jr <troycurtisjr_at_gmail.com>
Date: 2007-06-18 00:03:57 CEST

On 6/17/07, Carsten Koch <Carsten.Koch@icem.com> wrote:
> Troy Curtis Jr wrote:
> ...
> > and is a BDB. (Actually, running from RAM might improve FSFS enough
> > that I could switch to it!)
> ...
> > Ideas anyone?
>
> FSFS is a zillion tiny files, so what you can do is
>
> * use FSFS for your repository.
>
> * set vfs_cache_pressure to 0, so inodes will stay in RAM.
>
> * maybe preload the inodes to RAM by running a
> find /path-to-repository > /dev/null
> at boot time.
>
> If you still have lots of available RAM after that,
> you could preload even the data to RAM by running a
> find /path-to-repository -type f | xargs cat > /dev/null
>
> Carsten.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>

Thanks for the suggestions, but ultimately they are basically the same
that I have seen. The only issue with this is that it doesn't really
tell the kernel to keep particular inodes cached in RAM, and so they
will get replaced if you do enough other disk I/O.

This was the approach that I first investigated, but I would have to
constantly have to do this to make sure the repo data stayed in RAM.
Oh well.

Troy

-- 
"Beware of spyware. If you can, use the Firefox browser." - USA Today
Download now at http://getfirefox.com
Registered Linux User #354814 ( http://counter.li.org/)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jun 18 00:04:15 2007

This is an archived mail posted to the Subversion Users mailing list.