• State Suggested Answer
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 61 subscribers
  • Views 828 views
  • Users 0 members are here

Computer Specification for GenerativeComponents

Wayne Dickerson
Offline

Hi All,

lately we have been utilizing GC for our office tower concepts which has been very successful (Connect RC has been a great update)

I have found however it can get very slow. even with a simple model. so I am trying to find out what the best specification is for GC.

here is what I have tried it on:

PC1

Dell Precision 7910

  • 2 x Xeon E5-2650 v3 @ 2.3GHz (10 cores) (40 virtual CPUs)
  • 64GB Ram
  • Quadro K2200 4GB
  • 500gb SSD
  • Windows 10 creators edition

PC2

Dell Precision 5810

  • 1 x Xeon E5-2630 v4 @ 2.2GHz (10 cores) (20 virtual CPUs)
  • 32GB Ram
  • GeForce GTX 1080
  • 500gb SSD
  • Windows 10 creators edition

I have been running GC locally (on the SSD) with an out of the box install - no tweaking :)

During some simple operations the system will just crawl along even the mouse is delayed to a crawl.

Checking the usage and the CPU is really doing nothing, Ram usage is up above 10GB which is fine. Using TechPowerUp GPU-Z it shows the GPU load at low levels.

Just wondering if where to focus attention. is GC a graphic process or CPU.

Should I go for faster but less number of CPUs?

Should I go for SLI Graphic in direct x or open GL?

is it a driver issue?

Parents
  • 0 Offline
    Hi Wayne,

    GC itself is single-threaded. It is using the CPU (no GPU coding for GC-specific processes). Faster CPU should make a difference. Number of CPUs/cores will not affect GC directly; however, depending on scheduler and what other tasks are running on the machine, at least two CPUs may help maximize GC's usage of one. Available RAM will be an issue, as well, as memory swapping will impact performance.

    Please note that with CONNECT Edition, ABD's dynamic view caching uses multiple CPUs/cores as specified in the ABD Readme and uses GPUs for some geometry and graphics processing.

    Other Bentley applications (LumenRT, ContextCapture) may also benefit from specific hardware as outlined in their specific ReadMe files. Standard display graphics in View windows are using DirectX and will benefit from decent graphics support for larger models.

    If you note specific actions or situations where GC slows down to a crawl, please let us know so we can investigate and improve GC's performance.

    Regards,

    Volker

     

Reply
  • 0 Offline
    Hi Wayne,

    GC itself is single-threaded. It is using the CPU (no GPU coding for GC-specific processes). Faster CPU should make a difference. Number of CPUs/cores will not affect GC directly; however, depending on scheduler and what other tasks are running on the machine, at least two CPUs may help maximize GC's usage of one. Available RAM will be an issue, as well, as memory swapping will impact performance.

    Please note that with CONNECT Edition, ABD's dynamic view caching uses multiple CPUs/cores as specified in the ABD Readme and uses GPUs for some geometry and graphics processing.

    Other Bentley applications (LumenRT, ContextCapture) may also benefit from specific hardware as outlined in their specific ReadMe files. Standard display graphics in View windows are using DirectX and will benefit from decent graphics support for larger models.

    If you note specific actions or situations where GC slows down to a crawl, please let us know so we can investigate and improve GC's performance.

    Regards,

    Volker

     

Children
No Data
Communities
Support and Services
Training and Learning
Social Media