hi all, i''m considering using ZFS for a Perforce server where the repository might have the following characteristics Number of branches 68 Number of changes 85,987 Total number of files (at head revision) 2,675,545 Total number of users 36 Total number of clients 3,219 Perforce depot size 15 GB I''m being told that raid 0/1 XFS on linux would be the most efficient way to manage this repository, I was wondering if the list thought that ZFS would be a good choice? Thx! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20061114/89be45ec/attachment.html>
On November 14, 2006 7:57:52 PM -0800 listman <listman at burble.net> wrote:> > hi all, i''m considering using ZFS for a Perforce server where the > repository might have the following characteristics > > Number of branches 68 > Number of changes 85,987 > Total number of files > (at head revision) 2,675,545 > Total number of users 36 > Total number of clients 3,219 > Perforce depot size 15 GB > > > I''m being told that raid 0/1 XFS on linux would be the most efficient way > to manage this repository, I was wondering if the list thought > that ZFS would be a good choice?I was thinking of getting a fast car. I wonder if blue is a good choice? -frank
Listman, What''s the average size of your files? Do you have many file deletions/moves going on? I''m not that familiar with how Perforce handles moving files around. XFS is bad at small files (worse than most file systems), as SGI optimized it for larger files (> 64K). You might see a performance enhancement with ZFS. You''ll definitely see a management benefit from ZFS. -J On 11/14/06, listman <listman at burble.net> wrote:> > > hi all, i''m considering using ZFS for a Perforce server where the repository > might have the following characteristics > > Number of branches 68 > Number of changes 85,987 > Total number of files > (at head revision) 2,675,545 > Total number of users 36 > Total number of clients 3,219 > Perforce depot size 15 GB > > > I''m being told that raid 0/1 XFS on linux would be the most efficient way to > manage this repository, I was wondering if the list thought > that ZFS would be a good choice? > > Thx! > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss > > >
On Nov 15, 2006, at 1:09 AM, Jason J. W. Williams wrote:> What''s the average size of your files? Do you have many file > deletions/moves going on? I''m not that familiar with how Perforce > handles moving files around. >average size of my files seems to be around 4k, there can be thousands of files being moved at times.. the hierarchy is kind of strange for this data. we have maybe 4000 directories at the top level, each of which contains 2 subdirectories, which in turn contain 3 files each.> XFS is bad at small files (worse than most file systems), as SGI > optimized it for larger files (> 64K). You might see a performance > enhancement with ZFS. You''ll definitely see a management benefit from > ZFS.interesting, any other comments on this? i assume this is all going to be much better than the solaris 8 filesystem -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20061115/7db73d0b/attachment.html>
listman <listman at burble.net> writes:>> What''s the average size of your files? Do you have many file >> deletions/moves going on? I''m not that familiar with how Perforce >> handles moving files around. >>>average size of my files seems to be around 4k, there can be >thousands of files being moved at times..If the original question was for a Perforce server, not a client, then what kind of files stored in the repository should not matter. If I recall correctly, Perforce uses a database and not a profusion of small files so XFS should do quite well here (and probably ZFS too).
On November 15, 2006 4:40:36 PM +0000 Mattias Engdeg?rd <mattias at virtutech.se> wrote:> listman <listman at burble.net> writes: > >>> What''s the average size of your files? Do you have many file >>> deletions/moves going on? I''m not that familiar with how Perforce >>> handles moving files around. >>> > >> average size of my files seems to be around 4k, there can be >> thousands of files being moved at times.. > > If the original question was for a Perforce server, not a client, then > what kind of files stored in the repository should not matter. > If I recall correctly, Perforce uses a database and not a profusion of > small files so XFS should do quite well here (and probably ZFS too).There are 3 components to p4 performance. 1. branching complexity (addressed with raw cpu power) 2. database performance (addressed with RAM) 3. file xfer performance ("asynchronous" wrt db updates as long as the db is on a different disk from the files, so doesn''t affect concurrency but if lots of files are xferd to clients they may complain it''s slow if the disk subsystem is especially slow). in any event this is generally the least important aspect of p4 performance. This is why I challenged the question originally. -frank
Frank Cusack <fcusack at fcusack.com> writes:>1. branching complexity (addressed with raw cpu power) >2. database performance (addressed with RAM) >3. file xfer performance ("asynchronous" wrt db updates as long as the > db is on a different disk from the files, so doesn''t affect concurrency > but if lots of files are xferd to clients they may complain it''s slow > if the disk subsystem is especially slow). in any event this is > generally the least important aspect of p4 performance.I agree completely, but file system performance for small files should in any case not matter for a p4 server.>This is why I challenged the question originally.I''ve heard that red ones are supposed to be faster than other cars.