I noticed a few issues when running tortoisesvn on a large commit of files,
and just wanted to see if anybody had any input. I applied a commit of
5000+ files (copyright information) with tortoisesvn to a svn server running
apache.
After clicking the "ok" button on the commit window, tortoise appears to be
doing something for a few minutes before the modifications are sent and
logged by the apache/svn server as a CHECKOUT(this time lapse doesn't happen
when using the svn commandline). Then, tortoise starts listing the
"modified" files, and the server logs the CHECKOUT actions, and finally
tortoise lists the "sending content" file information and the svn server
logs the PUT actions.
During the commit process, tortoiseproc.exe takes up 550MB of memory and 1GB
of virtual memory. Also, it takes 10 minutes after the svn server logs the
final MERGE/DELETE for the tortoisesvn window to finally update. Once the
tortoisesvn window is closed, then the memory is released.
Is there any way to make tortoise a bit more resource friendly when doing
large commits? Does tortoisesvn really need 10 minutes after the commit is
finalized to update the tortoise window with successful commit information?
Please cc me directly in any response.
Thanks for creating a great interface to svn.
Jon
_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar – get it now!
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Fri Feb 17 00:29:32 2006