RE: Re: Re: Performance with many/few folders
From: Schuelke, Kai <Kai.Schuelke_at_eads.com>
Date: Thu, 23 Oct 2008 07:53:55 +0200
Well, thanks for your infos. I will opt for the folders then.
Regards
-----Original Message-----
On Wed, Oct 22, 2008 at 09:04, Schuelke, Kai <Kai.Schuelke_at_eads.com> wrote:
Thousands of directories within one, each directory containing a couple of files, will probably be similar in performance to a couple of directories containing many files.
If each person's work is isolated to only a few files at a time, then the many directories approach may be better (you can check out just the directories you need, and in Windows Explorer you won't need to go into the "big" parent directory often even if you do check the whole thing out).
OTOH (I just thought of this), if you're using Apache's path-based authorization, there can be a major slowdown with this approach if you check out the massive parent as it has to check each directory as it's checked out.
As a rule, I dislike both very flat and very wide directory layouts. I much prefer a strong, logical hierarchy. I have one directory in my main project which has about 900 files in it and there's no way for me to break it down further; it grates on my nerves for about a day every
>>Organize your tree the way it best represents your project/code/system.
Not as difficult as you might think with Subversion.
---------------------------------------------------------------------
---------------------------------------------------------------------
|
This is an archived mail posted to the TortoiseSVN Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.