http://use.perl.org/articles/08/12/22/0830205.shtml
More than twenty years of Perl development history has been migrated to Git and is available at http://perl5.git.perl.org/perl.git. Previously it used Perforce, and it was somewhat unfortunate choice for an open-source project.
According to joint press-release, “CollabNet, Inc. the leading provider of collaborative software development solutions, and VA Software Corporation (Nasdaq: LNUX), today announced the execution and closing of an asset purchase transaction whereby CollabNet purchased the SourceForge Enterprise Edition business from VA Software in consideration for an equity ownership stake in CollabNet.”
SourceForge Enterprise Edition supports CVS, Subversion and Perforce out of the box, and also provides possibility for integration with other SCM tools.
(via LWN.net)
It is well known that Google uses Perforce as its internal source management system (it has a source license). Niall Kennedy writes:
Google uses a company-wide Perforce depot with almost no developer branches. Each developer has their own NFS workspace readable by anyone in the company, including automated processes. An administrative process takes snapshots of each developer workspace including local development environments accessed over SSH. Files within these snapshots can be compared to checked-in data, encrypted, and archived.
Dan Bloch did a presentation at Perforce European User Conference, called “Performance and Database Locking at Large Perforce Sites”. It contains statistics on Google Perforce Depot, such as:
- More than 3000 users and 100Gb of metadata on one primary server;
- Hardware is an HP DL585 4-way Opteron with 128Gb of memory;
- Depot is on a NetApp filer;
- Metadata and journal on RAID-10 local disk;
(via Niall Kennedy: “Google Mondrian: web-based code review and storage”)