Hi devs, >From what I understand about the performance problems of WC-1 vs. WC-NG, and what I'm reading on this list, I expect(ed) a huge performance boost from WC-NG for certain client operations (especially on Windows, where the locking of WC-1 is quite problematic). Also, I knew I had to wait for single-db to see any real performance benifits. So after you guys switched on single-db, I eagerly gave trunk a spin... Now I'm a little worried, because I don't see any great speed increases (quite the contrary). Some details below.
Maybe it's just too early to be looking at this (maybe it's a simple matter of optimizing the data model, adding indexes, optimizing some code paths, ...). So it's fine if you guys say: chill, just wait a couple more weeks. I just need to know whether I should be worried or not :-). Some details ... Setup: - Win XP 32-bit client machine, with antivirus switched off. - Single-db client: tr...@992042 (yesterday), release build with VCE2008 - 1.6 client: 1.6.5 binary from tigris.org that I still had lying around. - Medium size working copy (944 dirs, 10286 files), once checked out with the 1.6 client (WC-1), once checked out with the trunk-single-db client. - 1st run means after reboot, 2nd run means immediately after 1st run. Numbers: 1) Status (svn st) 1.6 client 1st run: real 0m41.593s user 0m0.015s sys 0m0.015s 1.6 client 2nd run: real 0m1.203s user 0m0.015s sys 0m0.031s Single-db client 1st run: real 0m34.984s user 0m0.015s sys 0m0.031s Single-db client 2nd run: real 0m6.938s user 0m0.015s sys 0m0.031s 2) Update (no changes, wc already up to date) (svn up) 1.6 client 1st run: real 0m38.484s user 0m0.015s sys 0m0.015s 1.6 client 2nd run: real 0m1.141s user 0m0.015s sys 0m0.015s Single-db client 1st run: real 0m31.375s user 0m0.015s sys 0m0.031s Single-db client 2nd run: real 0m5.468s user 0m0.031s sys 0m0.015s Anyone able to take away my worries :-) ? Cheers, -- Johan
