Re: Node origins cache rewrite

On Jan 27, 2008 11:34 AM, Justin Erenkrantz <justin_at_erenkrantz.com> wrote:
> On Jan 27, 2008 8:08 AM, Mark Phippard <markphip_at_gmail.com> wrote:
> > Justin, what would ASF likely do? Would you be able to dump/load that
> > repository or would you just incur the disk space cost of the cache
> > that currently exists?
>
> We'd just burn the disk space, I guess. But, I'm not really sure it's
> worth an FS inode per SVN node-id...that just doesn't seem to scale.

If there was no fallback would you take the performance hit (which is
huge on your repository) or do the dump/load? Both options are so
bad, that I was suggesting it might be worth the effort to possibly
support both options to give a better upgrade path.

> > I imagine you could symlink that folder to a
> > volume that handles lots of small files more efficiently.
>
> We're not Google, so, throwing dedicated disks at it isn't a
> cost-effective option. =) -- justin

Well, I was suggesting some kind of filesystem format that handles
lots of small files efficiently. Depending on the format, you might
not need a lot of disk space to handle it.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org