CLion's "Building symbols" takes hours and block all operations when import large project,
I use CLion and bazel plugin import tensorflow serving project, it takes hour to build symbols, and it block my mac I cannot do anything.
it starts at 4:27 pm now is 6:23 pm still building
it takes too much cpu and mem
请先登录再写评论。
Yes, this is always the case it seems with CLion, with Windows (I think). Even if I create the bare bones c project in CLion it takes about 3 minutes and 22 seconds for CLion to perform "Loading CMake" and "Building/Saving Symbols" on my Windows 8.1 machine (i5-4310U @ 2.00 GHz). If I remote in (ssh) to a Ubuntu machine (v14, Intel Xeon E3-1225 v3 @ 4x 3.6GHz) which the DISPLAY is route to an instance of MobaXterm running on the same Windows machine (v8.1) it only takes 6 seconds.
I am using cygwin64 v2.5.1 on Windows. I am not sure why gcc is pretty slow on Windows, though I am not sure really why. I have heard that Windows takes a long time to create task whereas in Linux it is pretty quick. Though, this would only affect performance if CMake/gcc were spinning up a lot of task.
I haven't tried on my four year old MacBook Air, but it would be interesting to see its performance. The CPU on the Ubuntu is a bit better, but for a delta of over three minutes? Not sure that can account for all of the time delta.
Mark