Build hangs in Visual Studio, Release Build

[Mark Brudnak]

All, Trying to build fresh install of Chrono. Build of Debug version works fine.  Build of Release version is hanging:

1>------ Build started: Project: ChronoEngine, Configuration: Release x64 ------
1>ChElementBrick.cpp
1>ChElementBrick_9.cpp
1>ChElementShellANCF_8.cpp

Building with Visual Studio 2017.

I tried this on two different computers and experienced the same problem.  

Has anyone seen / solved this issue?

[Radu Serban]

Build times are highly dependent on your hardware.
For example, on my laptop (Intel Core i7-6600U 2-core) with Visual Studio 2017, building the core Chrono module takes over 40 minutes.  On the other hand, on my desktop (AMD Ryzen 7 3700X 8-core) with VS 2019, that is completed in under 3 minutes.
Note also that some larger files do take longer to compile. 

--Radu

--
You received this message because you are subscribed to the Google Groups "ProjectChrono" group.
To unsubscribe from this group and stop receiving emails from it, send an email to projectchron...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/projectchrono/f7ff80d7-a9b2-4f99-9572-d754b6bc71ddo%40googlegroups.com.

[Mark Brudnak]

Radu,

The build just hangs.  Like overnight it is still churning. I have a Core i7 with 16 logical cores and 64 GB of memory and SSD.

Mark

On Wednesday, August 19, 2020 at 6:07:58 AM UTC-4, Radu Serban wrote:

Build times are highly dependent on your hardware.
For example, on my laptop (Intel Core i7-6600U 2-core) with Visual Studio 2017, building the core Chrono module takes over 40 minutes.  On the other hand, on my desktop (AMD Ryzen 7 3700X 8-core) with VS 2019, that is completed in under 3 minutes.
Note also that some larger files do take longer to compile. 

--Radu

On 8/12/2020 3:48 PM, mali...@gmail.com wrote:

All, Trying to build fresh install of Chrono. Build of Debug version works fine.  Build of Release version is hanging:

1>------ Build started: Project: ChronoEngine, Configuration: Release x64 ------
1>ChElementBrick.cpp
1>ChElementBrick_9.cpp
1>ChElementShellANCF_8.cpp

Building with Visual Studio 2017.

I tried this on two different computers and experienced the same problem.  

Has anyone seen / solved this issue?

--
You received this message because you are subscribed to the Google Groups "ProjectChrono" group.

To unsubscribe from this group and stop receiving emails from it, send an email to projec...@googlegroups.com.

[Ezequiel León Zybert]

Same here....

[Ezequiel León Zybert]

I'm stucked there. It is on build process long ago

[Mike Taylor]

I'm using Visual Studio 2017 as well.  I have several of the code optimization flags set and the code takes a long time to compile on my laptop (several hours), but it does compile.  Lately, I've been using the the clang/llvm compiler through the Visual Studio 2017 extension (https://marketplace.visualstudio.com/items?itemName=LLVMExtensions.llvm-toolchain) and that has been compiling much faster on my laptop.  I'm not sure if that is an option for you to try as an alternative.

Best Regards,

Mike

[Radu Serban]

Could you (and anyone else experiencing such issues) provide the CMakeCache.txt file?  Maybe there's a clue in there.
Build times are slightly longer after the switch to using Eigen, but nothing like you report.

Thanks,
--Radu

To unsubscribe from this group and stop receiving emails from it, send an email to projectchron...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/projectchrono/4f8d8a8c-ee45-4bfa-8cfc-aef9218ff982o%40googlegroups.com.

[Alberto Luaces]

Maybe a red herring, but I have experienced in some low-end hardware
that compiling the ChElement* files could take a long time because of a
higher memory consumption, which makes the system to constantly swap.

Inspecting the memory usage of the machine when the build is likely hung
could confirm this theory.

[Alessandro Tasora]

In fact the ChElement* sources make a large use of linear algebra, and
this might put some pressure on the template expression machinery hidden
in the Eigen matrix library (we recently switched to Eigen from our own
matrix libraries, there are many benefits but one drawback is that Eigen
requires long building times especially for the way it used templating
to simplify matrix expressions at compile time)

Alessandro Tasora