Re: CPU usage during commits

On May 24, 2006, at 7:44 AM, Ryan Schmidt wrote:

>
> On May 24, 2006, at 16:02, Sinang, Danny wrote:
>
>> In http://svnbook.red-bean.com/nightly/en/svn-book.html , it says :
>>
>> Specifically, each time a new version of a file is committed to
>> the repository, Subversion encodes the previous version (actually,
>> several previous versions) as a delta against the new version.
>>
>> On average, we'll be checking in 10 MB PDF or TIFF files . Will
>> this consume a lot of CPU or Disk I/O ? If so, how much ?
>
> Only BDB repositories do this. FSFS repositories do not do this.
>
>

now i'm confused. for FSFS repositories what is the sequence of
operations for large binary files? i thought it was:

1) compare new version to previous version held in the working area,
generate delta
2) transfer binary delta to repos and store

what is the sequence for a new user checkout ? is the latest version
recreated from the layers of deltas in the repos?
is a pristine latest version kept in the repos?

i guess i'm confused as to where all these deltas occur and how they
are used.

note that binary deltas are time consuming and too many are going to
slow the whole mechanism down

> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 24 18:16:46 2006