[cvsnt] Multiple repositories
bo.berglund at telia.com
Wed Mar 8 21:27:37 GMT 2006
On Wed, 8 Mar 2006 15:42:30 -0300, "Flávio Etrusco"
<flavio.etrusco at gmail.com> wrote:
>On 3/8/06, Tony Hoyle <tony.hoyle at march-hare.com> wrote:
>> John Hall wrote:
>> > Unless it moves/renames those temporary files to overwrite files in the
>> > repository. If the temp folder is on a different drive then it needs to
>> > copy, then delete rather than move, which is slower.
>> It doesn't. The temporary files are just a mirror of the client sandbox
>You mean on 'cvs update', right? What about tagging and commit?
>Anyway, it's good to hear this from you, since in my experience even
>'cvs update' is largely slowed down if the temp folder is in another
>partition. I'll try to investigate it further...
Please consider that partitions are on the same physical drive. So if
you have the repository on one logical drive and the temp files on
another logical drive on the same physical drive, you will force the
system to slow down.
This is because inbetween operations on the real files and the temp
files the single disk drive head must physically move between
different sections of the disk and this will significantly slow down
disk intensive operations like CVS uses.
Best performance should be obtained with two *physical* drives with
the repository on one and the temp dir on another. This way if no
other software is involved the disk heads will stay in the same region
on the drives and the data transfer will be limited only by computing
and actual disk read/write speed taking positioning out of the
As a comparison, when one installs a database on a MS-SQLServer it is
always recommended to keep the database file on one *physical* drive
and the log file on another *pysical* drive in order to maximize
performance. Keeping them on the same drive will force the read head
jump slowdown described above.
(Bo Berglund, developer in Sweden)
More information about the cvsnt