We have upgraded from TeamCity 8 to 9 and our .net builders increased their build time from 3 minutes to 15 minutes.
We started investigating this issue, by doing the next steps:
Enabled "Performance Montioring" build feature - and we saw the disk io is maximum 9% and cpu is maximum 40% (our build agents have 2 cores and 4gb of memory)
Enabled .net runner logs to see if something in msbuildbootstraper takes lots of time.
After 2 days of investigation (we checked our antivirus, io, cpu and memory and every looks fine) we started to suspect that MsbuildBootstrap of jetbrains takes most of the time.
We took one build, that with "msbuildbootstraper" takes 32 seconds and switched it to "Command Line" runner and called msbuild our selves and the build time decrease to 5 seconds.
We are currently thinking about downgrading to version 8 of teamcity or moving to tfs, before doing so - do you have any suggestions for fixing/throubleshooting this?
And we found the solution: https://teamcity-support.jetbrains.com/hc/en-us/community/posts/206819485-JetBrains-BuildServer-MsBuild-Bootstrap-exe-9-0-9-9-0-14-hangs-for-30-seconds-on-TeamCity-9-0
As the link above says, add this configuration to MSBuildBootstraper:
<configuration>
<runtime>
<generatePublisherEvidence enabled="false"/>
</runtime>
</configuration>
More info here: https://confluence.jetbrains.com/display/TCD9/Common+Problems#CommonProblems-Problemswith.Net-relatedTeamCityTools
Related
first time working with gem5,according to gem5.org the following build command should take about 15 minutes or so to complete, build/X86/gem5.opt -j9. But its been more than an hour since the build started and its not complete yet, has anyone experienced the same issue? is it normal? My machine has 8 cores and I've allocated 16 gigs of memory for VMware on which am running the build. Can it be a hardware problem such as not enough memory?
So far I have started the build process from scratch a few times with the same results, I've also tried it on a different virtualization platform (Virtualbox) but Its taking the same amount of time to build.
Thanks!
I have a Lenovo Z51-70 laptop (Windows10). it had 8GB RAM by default and SSHD. When I used to compile large projects 20K c++ files Task Manager always showed 90-100% CPU utilization. A week back I upgraded SSHD to SSD and 8GB RAM to 16GB RAM for gaining speed in the compilation. But build time hasn't improved (it is almost same) but Task Manager always shows roughly 50% CPU utilization. Why it is not able to utilize anyway near 90-100%? and why same build on SSHD & 8GB RAM always used to consume roughly 90-100% CPU utilization? It is not specific to a particular build system, i have tried MSBUILD, NINJA. All build system show same CPU utilization. I have tried to compile different projects for excluding any reason which may be the project-specific.
Any thoughts?
After upgrading a grails application (usage of multiple inline plugins, > 130 controllers, > 140 services, > 180 domain classes, > 600 GSPs) from 2.5.4 to 3.2.8:
grails run-app before update: 2:10 minutes.
grails run-app after update: 5:50 minutes.
Most of the time the grails 3.2.8 run-app is hanging at ":boot-run". Especially after spring security core has initialized (about 2 minutes after start) it hangs for about 4 minutes. Additionally the CPU usage is very low compared to grails 2.5.4.
The test was repeated with different machines and faced similar results (Mac, Linux and Windows machines).
What can be the reasons for this behaviour?
That's incredible: If you restart intellij before running ´grails run-app´ for the very first time, the boot time is 2 minutes with grails 3.
Do not use the restart button in intellij 2017.1.1.
Update
There is definitely some memory leaks in runtime environment of IntelliJ.
Updating to Java 8 SDK improved situations a lot.
Adding "bootRun { jvmArgs = ["-Xmx4096m"] }" to build.gradle was key succes.
App starts now in 30 seconds. I would recommend to upgrade to grails 3.
I need to run an intensive CPU task that maxes all cores of my CPU to 100%.
After a few days of running this task, I find that the machine becomes unresponsive and I am no longer able to SSH into it. I then have to restart the machine and begin the task again. This task could take several weeks or even months to compute.
I'd like to find a way to run this task to completion.
I've tried running the task on Debian 8 and Ubuntu Server LTS. Both of these operating system exhibited the same problem. I thought about running the task inside a Virtual Machine and using Cron to snapshot it every hour, but this seems quite extreme and would suffer an overhead.
Why is it that my machine is unstable?
Could it be due to power fluctuations?
Should I try under-clocking the CPU?
Thanks
I'm using a VM with VMware Player to write code and compile.
As my current program is huge, the compilation takes a while to be done (upto 5 minutes)
using 25% of my 4 cores CPU on my host = 100% of one core.
It seems that the VM is limited to use 1 single core.
Is there a way to optimize the number of cores a VM can use?
I'd like to use 50% or 75% of my 4 cores CPU.
Thanks
It sounds like you're limited by the number of parallel build tasks you can run, not the VM CPU configuration, e.g., by default, make will run a single step at a time. Try running several steps in parallel, e.g., run make -j4 or equivalent for your build system.
On a separate note, a VM may be more overhead for you than you might like; consider using Docker to host your development environment.