RE: Re: TSVN slow merges (help!)
From: Joel Low <joel_at_joelsplace.sg>
Date: Sun, 15 Jun 2008 06:48:36 +0800
Hello Stefan,
One thing which potentially is of some use is the changes in compiler code generation across VC versions (You mentioned you used VC2008, svn project uses VC6). VC6 had no stack frame checking (/GS) and other security checks which may slow down execution. The other possibility is the use of exception handlers. I believe TSVN uses C++ for its UI and stuff, so cl may have assumed that the rest of the svn code (in C) would have exceptions applied to it. That will definitely add considerable amount of overhead. Even if the code was compiled as C, /EHa still generates code for __try/__except which would add the same amount of overhead. Finally, the last possibility will be the use of the safe C runtime library. The safe parameter validation et al will definitely contribute to processor overhead.
You didn't mention anything about CPU usage, so I'll assume that the CPU usage went up (and hence assume all of these)
Hope this helps.
Regards,
-----Original Message-----
Jean-Marc van Leerdam wrote:
Yes, each packet sent from my own built client is sent a few miliseconds later. It's not just a few big pauses in between, it's between every single packet.
> How does the TSVN Gui perform this merge? Is it also 5 min 17, or is
It's the same as with my own built CL client. Also aroung 5:17.
> IIRC in the past TSVN (or the SVN linbraries, I can't remember) has
Already checked that. But the debugger doesn't show any dll loads or unloads during a merge (only when the command starts, but that's expected and has nothing to do with the delay).
Thanks anyway for your suggestions.
Stefan
-- ___ oo // \\ "De Chelonian Mobile" (_,\/ \_/ \ TortoiseSVN \ \_/_\_/> The coolest Interface to (Sub)Version Control /_/ \_\ http://tortoisesvn.netReceived on 2008-06-15 00:48:56 CEST |
This is an archived mail posted to the TortoiseSVN Dev mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.