I don't have exact timings here but 30 min to compare vs seconds is blatent.)ĪSSERTION: I do not believe winmerge is just pulling the 'top' 1M of files.
I'm running a binary (1M limit) compare on 200files as I type this and it is taking similar speeds to a full read 40Gx2 data operation (by rough appearances. Taking the 'top' 1M of 200 files and pulling it over USB (even USB2) from 2 sticks should take SECONDS.īUG/ISSUE: the speed of the compare hasn't seemingly changed at all. So I thought 64Mx200=12G might still be too high for me to notice an improvement, so I will change the binary compare limit to a minimal 1M. Dropping from full to 64M didn't seem to improve speed. I then went to settings and changed to binary compare (and left the 64M compare limit) and started again. But I saw the speed as it was proceeding, which is important. I started one and it went very slowly and I stopped. USB can transfer data fine, but a complete read of 40G from 2 sticks would normally take time, as expected (esp when one is USB2 which one of them is).Ī full content compare of this situation is probably 30 minutes or more (I haven't waited to find out). I mention USB sticks to indiate a data transfer constraint for this issue report (which might cause the problem to not be noticable on a direct PCI/SSD situation). Most of the files are very large in size (200M-500M) and there are only a comparative small number of 200 files.
Somebody checked in a bunch of spaces at the end of a line.ISSUE: I believe winmerge is reading or processing full file data even when, during a compare, it is only set to use a small 'compare limit' and thus SHOULD only be reading the 'top' x MB of a file.Ĭomparing about 40G of files on two USB sticks. Set your style and have the IDE conform the code to it for you. You are using an IDE which doesn’t do code cleanup for you. Seriously, there are diff tools that can’t do this in 2009? I would have never guessed. Was your diff tool written in 1990? Because WinMerge has been ignoring whitespace, blank lines and CR vs CRLF for at least that long. I love locking, because then I can just set Visual Studio to conform the code to the way I like, and the next guy the same. Tried and true locking is the best solution when you can easily divide the work between modules. You aren’t writing the freaking Linux kernel!!! You don’t need merging, it just causes all kinds of problems. You are using a merging repository with 10 developers. Didn’t you get the memo that those suck? They eventually trend toward unmaintainable. You are using a language with ASP-style syntax. Sounds to me like you are complaining about the symptoms, not the problem.
0 kommentar(er)
