Book a Demo

Author Topic: Performance: Get All Latest takes too long--42 Min  (Read 2752 times)

tim-southerland

  • EA User
  • **
  • Posts: 25
  • Karma: +0/-0
    • View Profile
Performance: Get All Latest takes too long--42 Min
« on: December 07, 2010, 03:21:16 am »
"Get All Latest" takes 42 Minutes for my architects. This is too long to be practical.  Is there a way to get EA to use more memory to speed "Get All Latest" process up?

Configuration:  EA v8.0.858, WinXp sp2, Subversion 1.6.1, 1.86ghz, 2gb RAM, 100Mpbs dedicated Network, non-secured http to svn, no sql backend.

We have a model w/ more than 7k elements and 10k connections.  Standard operating proceedure is to run "Get All Latest" in the morning so that architects can be sure that they have all changes from the previous day.  Architects are instructed to use "Import only files that have changed" .  "Get All Latest" causes the CPU to max out, while EA only uses 128MB of 2GB of memory ( w/ > 1Gb free).

It appears that small changes (adding one or two elements w/ connections) to a diagram w/ many elements and connections modifies each diagram, require the tool to re-import each connection/element again during "Get all Latest" operation.  Also, killing the "explorer.exe" process temporarily while "Get all Latest" is executing appears to speed the process up.

Architects could benefit from a function that allows them to get all the latest for a particular branch, rather than an entire project or single package.

lubos

  • EA User
  • **
  • Posts: 101
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Performance: Get All Latest takes too long--42
« Reply #1 on: December 22, 2010, 12:48:38 am »
>>Architects could benefit from a function that allows them to get all the latest for a particular branch, rather than an entire project or single package.

This can be solved by a simple  script calling Package.VersionControlGetLatest(true) for all packages recursivelly.

But I vote for supporting this functionality directly by EA too.