[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: cvs tag performance
From: |
Rahul |
Subject: |
Re: cvs tag performance |
Date: |
14 Jul 2005 13:16:39 -0700 |
User-agent: |
G2/0.2 |
run "iostat -x 3" or equivalent to monitor the disk for contention.
Look for stats like (see man iostat). On Linux :
avgqu-sz
The average queue length of the requests that were issue
to the device.
await
The average time (in milliseconds) for I/O requests
issued to the device to be served. This includes the time
spent by the requests in queue and the time spent servic-
ing them.
svctm
The average service time (in milliseconds) for I/O
requests that were issued to the device.
If you see large queue sizes and response times you know you may have a
disk storm being generated when tag command modifies files. Since CVS
doesn't do any concurrent tagging (like mutliple threads or processes
operating on individual dirs etc) you will have to look at faster disk
option.
When you say "it's suddenly taking too much time" there must be other
disk activity kicking in that's causing disk contention when tag
command shows up.
Regards,
===
Rahul Bhargava
CTO, WANdisco
http://www.wandisco.com/cvs