[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALkWK0ngNM-zrybHOtFGzm5aVnkFMPn1DP0h=2aUf=7b9_sh8A@mail.gmail.com>
Date: Fri, 5 Apr 2013 22:26:15 +0530
From: Ramkumar Ramachandra <artagnon@...il.com>
To: Jan Kara <jack@...e.cz>
Cc: linux-kernel@...r.kernel.org, Junio C Hamano <gitster@...ox.com>,
Thomas Rast <trast@....ethz.ch>,
Duy Nguyễn <pclouds@...il.com>,
Jeff King <peff@...f.net>,
Karsten Blees <karsten.blees@...il.com>,
Git List <git@...r.kernel.org>
Subject: Re: Beyond inotify recursive watches
Jan Kara wrote:
> Hum, I have somewhat hard time to understand what do you mean by
> 'magically optimized syscalls'. What should happen in VFS to speedup your
> load?
In retrospect, I think this is a terrible hack to begin with. Tuning
the filesystem specifically for git repositories is inelegant on so
many levels, I can't recall why I ever thought it would be a good
idea. Like all software, Git has scaling issues with ultra-large
repositories. Too many stat() calls is just one of the problems:
there will be too many objects to do any operation at reasonable
speed, and the overall UX would just suck. Instead of growing to a
huge monolithic beast that spawns off worker threads for everything
and ultimately dying off, I've decided that git should take a
different direction: it should work with well with many small
easily-composable repositories. I've started work on this already,
and it looks very promising.
Let the filesystem people do what they do best: optimizing for all
applications uniformly.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists