32 replies to this topic

[CodingGorilla]

I have a workspace that has over 50,000 files, and it takes on the order of 20+ minutes for the Pending Changes view to "Find changes in the workspace". Is this normal? Is there anyway I can speed this up??

[cidico]

Hi Gorilla!

Are you using the "Compare file content instead of timestamps" option in the Preference -> Other Options?
Maybe unchecking this option could give you a performance boost

[CodingGorilla]

Hi Cidico, Nope that option is not checked. That's what puzzles me, I don't understand why it would take so long.

[cidico]

If you use the "cm findchanged", "cm findcheckout" do you get the same response time?

[CodingGorilla]

Nope, those both return in just a second or so. I can see, using Process Monitor, that plastic.exe is grinding through all the files (almost acting like it's comparing them) and also a lot of temp files too, so I'm not sure what it's doing. I can provide the traces from Process Monitor if that would be helpful.

[cidico]

I had a problem like this one you're saying but with a lot less files.

But it was happening randomly.
After some builds this seems to be solved.
I was thinking that could be my work machine that was slow since it was not happening at home (where my machine is MUCH MUCH MUCH more powerful).

Let's wait for our savior Manu!

[CodingGorilla]

Actually, after thing about it and double checking, both of those cm commands you asked about return no results at all. They should be returning about 2000 changes.

[manu]

sorry for my late answer,

let's see I need you to do the following:

1) Post a screenshot of you pending changes view options panel, I want to review your enabled search options.
2) If you have the "Show manually renames/mode items" option enabled, disable it and refresh the view, tell me if it's faster.

[CodingGorilla]

Could it have been just the sheer number of changed files that needed to be committed? At the time I had over 2500 files that needed to be committed; after the commit it seems to be functioning at a normal pace.

[manu]

I'm not sure, can you tell me if they were checked-out items or only "changed"?

Do you have the option "Compare file contest instead of time stamps when determining changed status" enable at the Plastic SCM preferences wizard?

[CodingGorilla]

Here's a screenshot of my pending changes option;

http://screencast.com/t/rHBCBwoCW

And here's my "Other options:

http://screencast.com/t/NZ3Zh1bpdg

The files were not checked out, they were just changed.

[manu]

Thanks for the info CodingGorilla, I'll try to reproduce the issue in my computer with a huge number of changed files.

If it happens again to you don't hesitate in contact us, I'll get connected with you to debug the issue.

[CodingGorilla]

I just realized the workspace was being accessed through a junction, I wonder if that also had an impact. I changed it so it goes through the real path, so I'll keep an eye out and see if it recurs.

[manu]

Ok! Thanks for the extra info!

[psantosl]

Hi there,

We test with larger workspaces, about 400k files. In fact we have customers using wks this size on a daily basis.

My personal workspace is about 30k files and once the disk is warmed up, it takes two seconds to find changes.

We've to figure out what is slowing you down!

[Olaf Kober]

Hi!

We had similar performance problems with pending changes in a workspace with about 8000 files, where ~2000 files were changed. Sometimes it took about 30 seconds to update.

In our case it seems that our virus scanner (Symantec Endpoint Protection) was slowing it down. Excluding our workspaces and also the temp-folder from Realtime Protection does the trick. Now we have refresh times of 1-2 seconds.

[manu]

Brilliant! Very interesting!

Thanks for sharing it!

I hate anti-virus software

[immitev]

We have similar issue with large number of private items (maybe tens of thousands). Unchecking the "Show private items" in the client made a huge difference in performance. No more waiting for 20 or more minutes -> the updates now take a couple of seconds. Unfortunately this option can't be used with the Visual Studio integration and basically we are now doing check-ins outside VS.NET. It's not very convenient, but at least, we can check-in quickly

[manu]

Hi immitev,

can you please issue the following command and postus the putput:

cm iostats

[immitev]

Performing network tests with server: 10.10.10.144:8087. Please wait...
Upload speed = 328 Mbps. Time uploading 16MB = 390ms. Server: 10.10.10.144:8087
Download speed = 680 Mbps. Time downloading 16MB = 187ms. Server: 10.10.10.144:8087

Performing disk speed test on path: C:\Users\imitev\AppData\Local\Temp\PlasticSCM_IOStats. Please wait...
Disk write speed = 103 MB/s. Time writing 512MB = 4960 ms.
Disk read speed = 1822 MB/s. Time reading 512MB = 281 ms.