Jump to content

Performance of Pending Changes in a very large workspace


CodingGorilla

Recommended Posts

Attempt 1:

Total Files Listed:

46088 File(s) 7,266,578,083 bytes

24422 Dir(s) 3,495,960,576 bytes free

command took 0:0:15.49 (15.49s total)

The Pending Changes (with enabled "Show Private Items") takes 6 minutes and 30 seconds for 34214 private items

Attempt 2:

Total Files Listed:

46089 File(s) 7,271,622,056 bytes

24422 Dir(s) 3,490,832,384 bytes free

command took 0:0:2.46 (2.46s total)

The Pending Changes (with enabled "Show Private Items") takes 7 minutes and 20 seconds for 34214 private items

NOTE: The Pending Changes refresh with disabled option is almost instant.

I tried the BAT command several more times in a row and got respectively 4.04s, 1.54s, 1.56s and 1.56s seconds

Link to comment
Share on other sites

  • 1 month later...

Hi,

Would like to check if there are plans to address this performance issue, since it basically makes check-ins from inside VS.NET unusable.

In most situations we don't mind using the PlasticSCM client, but the scenario which is somewhat annoying is when new files are added from within Visual Studio, there is no easy way to check-in them. Possibly it could be implemented a mode that doesn't do a full traversal of private items, but just displays as added the newly added files in the solution?

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...