15 messages in com.perforce.perforce-userDepot wasting space?
FromSent OnAttachments
Koht...@ntc.nokia.com27 Jan 1998 05:30 
Laur...@perforce.com27 Jan 1998 09:12 
Davi...@home.chat.net27 Jan 1998 10:08 
Koht...@ntc.nokia.com28 Jan 1998 08:39 
RobC...@within.com28 Jan 1998 11:07 
Laur...@perforce.com28 Jan 1998 11:13 
Koht...@ntc.nokia.com29 Jan 1998 07:12 
Koht...@ntc.nokia.com29 Jan 1998 09:21 
TomB...@ebc.ericsson.se29 Jan 1998 23:39 
nic...@aperture.comnickp30 Jan 1998 05:13 
TomM...@sybase.com30 Jan 1998 07:03 
Koht...@ntc.nokia.com31 Jan 1998 11:59 
Mark...@voro.lbl.gov31 Jan 1998 14:31 
Matt...@geoworks.com02 Feb 1998 17:28 
Koht...@ntc.nokia.com04 Feb 1998 04:30 
Subject:Depot wasting space?
From:TomM...@sybase.com (TomM@sybase.com)
Date:01/30/1998 07:03:53 AM
List:com.perforce.perforce-user

Hi Tom,

Fotunately, that's not true. You can get a DLT system from Quantum that uses 20Gb (uncompressed, 40 Gb compressed) tapes...

Tom.Bjorkholm at ebc.ericsson.se on 01/30/98 02:39:26 AM

To: Marko.Kohtala at ntc.nokia.com cc: laura at perforce.com, perforce-user at perforce.com (bcc: Tom Madigan/SYBASE) Subject: Re: Depot wasting space?

Hi, For most of us the the action of retrieving ('p4 sync') files from the depot is much more common than the action of submitting files. (Maybe Marko is an exception...). The design of Perforce that keeps the latest files (head revision) as full versions and older files as diffs to the newest, is normally the fastest. This is the way I like it to be. However, Marko has pointed out another consideration: How can we fit the depot on our backup media? For commercial users like myself, I do not really care if the depot uses 4 GB, 8 GB or 20 GB -- disk space is cheap. But the largest backup media that you can get at a low cost is a 4 GB (or maybe 8GB) DAT tape. To be able to simply automate the backup (using cron) the backup should fit on a single tape. Maybe Perforce should have an option to generate a more compact representation for backup purposes? /Tom

On Thu, 29 Jan 1998, Kohtala Marko wrote:

This is the way Perforce works. Whether or not you view it as a flaw depends on your expectations of performance.

From our perspective, maximizing developer productivity by providing fast access to file contents is a more important requirement than saving every inch of server disk space. And for most of our

In this case, you both waste space and make Perforce slower.

I am quite sure the submit would be considerable faster if the server did not create and update the 20M of excess RCS files per branch. The duplication of same file contents brings no benefit for any other operations either.

--

--- Marko Kohtala - Marko.Kohtala at ntc.nokia.com, Marko.Kohtala at hut.fi

--------------------------------------------------------------------- Tom Bjorkholm Ericsson Business Networks AB Sr. Software Designer NA/EBC/DN/NT, Nacka Strand (C++ and UN*X) 131 89 Stockholm, Sweden phone: +46 8 422 1348 / fax: +46 8 422 2080