Veracity Q&A home login about faq

What is the maximum allowable working copies while maintaining acceptable performance in the Tortoise client? When I open a folder containing 50+ working copy folders, Windows Explorer freezes.

Computer Specs:

  • Windows XP
  • Intel Core i7 CPU M 620 @ 2.67 GHz
  • 3GB RAM

There is a noticeable lag with as few as 5-10 working copies. Regardless of the number of working copies, Veracity shouldn't be able to slow down Windows to this level.


Can anyone else confirm similar performance issues?

asked Feb 09 at 14:20

Jace%20Browning's gravatar image

Jace Browning
676213245

edited Feb 10 at 06:01

For clarification, do you mean 50 folders, each of which have a .sgdrawer, or one folder that has a .sgdrawer folder, as well as 50 other folders?

(Feb 09 at 15:15) Jeremy Sheeley ♦

@Jeremy Sheeley, "50 folders, each of which have a .sgdrawer". They are also each from a different repository.

(Feb 09 at 15:19) Jace Browning
1

I've experienced similar behavior. I've got a folder with about 20 subfolders (each a working copy of a [different] repo).

Even worse there have been a couple times where my Windows starts running out of resources (context menus stop showing, or display slow, or all black, no icons and folders in explorer, etc.) I don't want to say it is Veracity related, but it didn't happen before Tortoise was installed.

It is rare, happening maybe three times now, but a reboot was necessary.

(Feb 10 at 07:08) jslutter

Also, it isn't always that my Windows Explorer freezes/slows, the behavior observed is on par with a resource leak of some sort.

(Feb 10 at 07:10) jslutter

@jslutter, Are you on XP as well?

(Feb 10 at 09:10) Jeremy Sheeley ♦

Windows 7 (x64 install of Windows and Veracity 1.5.1)

(Feb 10 at 09:12) jslutter

I've reproduced the problem here, and I see on my system that the veracity_cache.exe program is hitting the "virtual size" limit of 2 GB. If your system starts to get bogged down, killing the veracity_cache process will help.

(Feb 10 at 10:44) Jeremy Sheeley ♦

@Jeremy Sheeley, killing veracity_cache.exe did not improve system performance for me. The process also restarted upon opening a new window containing working copies. It appears I cannot store more than a few working copies in the same folder and expect Windows Explorer to be responsive.

(Feb 10 at 12:40) Jace Browning
1

Almost the same problem. Running WinXP, and with just a few (about 5) folders that are veracity working folders of different repositories. Explorer freezes frequently. Killing veracity_cache.exe (all 2 of them, or even 3 at times!) helps, but only for a short period of time (haven't timed it, but I will the next time).

(Feb 12 at 13:12) AASoft
1

Thanks for the updates, guys. Getting this sorted out is now my top priority, and I'll update this thread when there's a new build to try.

(Feb 13 at 10:12) Jeremy Sheeley ♦
showing 5 of 10 show all

I've ivestigated and reproduced this issue, which at its core was about veracity_cache creating too many threads. A fix has been implemented, and a nightly build is now available for testing, which includes the fix. You will need to uninstall your current build and make sure that veracity_cache.exe is killed before upgrading to the nightly build. Please respond here if the nightly build doesn't fix the issue for you.

link

answered Feb 17 at 12:56

Jeremy%20Sheeley's gravatar image

Jeremy Sheeley ♦
1761410

Performance seems better in the nightly build. A folder containing 120 working copies takes ~5 seconds to initially load all the icons then ~2 seconds to open the folder thereafter.

(Feb 20 at 07:48) Jace Browning

@Jeremy Sheeley, any idea when this bug fix will be incorporated into a release? This issue is still crippling any developer using 1.5.1.

(Apr 03 at 11:08) Jace Browning

The fix will be in the next release, but I can't make a promise about when that will be.

(Apr 03 at 11:28) Jeremy Sheeley ♦

@Jeremy Sheeley, Ok. Just making sure you understand that 1.5.1 is literally unusable for my team as it crashes Windows Explorer.

(Apr 04 at 09:06) Jace Browning

@justus87 We understood that the 1.5.1 release was unusable for you in February. That's why we published a nightly with a fix. Is that not working?

(Apr 04 at 09:27) Ian Olsen ♦♦

@Ian Olsen, yes the nightly build works (thank you!), but I'm finding that preventing people from visiting veracity-scm.com in search of a download link is difficult. I get questionable looks when I tell people that the official download is broken and we have to use an experimental build.

(Apr 04 at 10:05) Jace Browning
1

@justus87 Okay I get it. I can understand those questionable looks. On the off chance it makes people feel better about the "experimental build" until the next release, I'll say this: the tortoise-specific fix in that build hasn't changed at all since we published it. It's solid. It will almost certainly be identical in the next "official" release. I understand my saying that here doesn't really solve your problem, but I hope it helps, if only a little.

(Apr 04 at 11:34) Ian Olsen ♦♦

@Ian Olsen, just an update: I've moved one of my machines to Windows 7 and performance/behavior of the nightly build is very different when opening a folder with 70+ working copies:

Windows XP: Explorer "freezes" for 5+ seconds then folders with Veracity accents start to appear. Scrolling performance is degraded.

Windows 7: No impact to Explorer performance. All folders are visible immediately. Veracity accents gradually start appearing over the next 30-60 seconds.

Perhaps this issue is more related to differences between XP and 7?

(Apr 10 at 09:51) Jace Browning

@justus87 As I understand it (and Jeremy can chime in if I'm wrong) there are significant differences between explorer in XP and Vista/7, with respect to a tortoise shell extension. The bug we're talking about here affected both, but Vista/7 is generally better behaved.

(Apr 11 at 11:54) Ian Olsen ♦♦
showing 5 of 9 show all
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×16
×11

Asked: Feb 09 at 14:20

Seen: 530 times

Last updated: Apr 11 at 11:54

powered by OSQA