Re: performance issues over time

> Are you sure the script did not send any more data in the meantime that
> the server was waiting on? The entire diff was sent in those first three

> seconds?

Yes. I used ethereal to do the network trace and captured the entire
cycle of the commit. For 3.5 minutes, there were no network packets
transfer between the server and the client machine.

> At any rate, wait until the script finishes running and see if you still

> experience those problems. My point is that it's difficult to isolate
> the variables until then. You are not likely to see that sort of
> sustained pounding during everyday use.

Unfortunately, at this rate it'll take 40+ days to complete the script.

> If you still see problems, you may want to read "Berkeley DB
> Configuration" in the Subversion book under Repository Administration
> and also read the comments in DB_CONFIG.

Yup. That fixed it. I temporary paused the script and changed DB_CONFIG
to
the following parameters and ran svnadmin recover and now the commit is
happening every 2 second.

set_lk_max_locks 4000
set_lk_max_lockers 4000
set_lk_max_objects 4000
set_lg_bsize 1048576
set_lg_max 8388608

Thanks for your help!

Regards,
John Liao

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 4 00:15:14 2004