Bug 2376 - Our MonoTouch solution builds extremely slowly (5 - 10 minutes after even minor changes)
Summary: Our MonoTouch solution builds extremely slowly (5 - 10 minutes after even min...
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Deployment ()
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-12-06 18:31 UTC by cmmouritsen
Modified: 2013-12-05 18:34 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

kill log (72.44 KB, text/plain)
2012-01-03 17:31 UTC, Brian LeBaron

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description cmmouritsen 2011-12-06 18:31:57 UTC
Our MonoTouch solution builds extremely slowly (5 - 10 minutes after even minor changes). It is a large solution with several projects, but it didn't always build this slow. It seems something has changed.
Comment 1 Brian LeBaron 2011-12-07 19:53:29 UTC
We have a solution with 46 different projects. Build times with a change in the startup project were around 2 minutes. Last week we added some files and a new assembly reference to dependent projects. Now a change in the startup project takes ~8 minutes to build. The build will just hang building the main startup project. All dependent projects haven't changed so they aren't built. One core of the CPU goes to 100% and MD just sits there and then eventually finished after a ~8 minute wait. We've gone through the revision that causes the increase in time, the revision before builds fast, the revision after builds slow. Is there something that we could be doing that is causing the slow down? Is there something that we could look at that would tell us what it is doing while it is just sitting there?

Comment 2 Miguel de Icaza [MSFT] 2011-12-11 21:42:12 UTC
You can send the QUIT signal to the MonoDevelop process, that will dump into its standard output the stack traces of all the threads in the process.

The output is typically logged into the process Logs file which you can access from the "Console.app" in MacOS X.     

You could also try reducing your solution to the smallest test case that reproduces this problem and paste it on a new bug and flag the content as private.
Comment 3 Brian LeBaron 2012-01-03 17:31:51 UTC
Created attachment 1121 [details]
kill log
Comment 4 Brian LeBaron 2012-01-03 17:50:30 UTC
When it hangs it appears to be only using one core of the CPU. The same hang also seems to happen during a clean.
Comment 5 Brian LeBaron 2012-01-20 19:05:10 UTC
I was able to speed up the build by doing a few different things:
- Removed all direct assembly references and replaced them with project references. This showed the biggest improvement.
- Removed all unneeded references.

We now have the build time to right around 2 minutes. Which still feels extremely slow. Were you able to see anything from the log? If needed I can give you access to our solution.
Comment 6 Miguel de Icaza [MSFT] 2012-01-20 21:10:50 UTC
If you could provide the project to us we could take a look at what is sowing down the build so much for you.

Please contact me at miguel@xamarin.com
Comment 7 PJ 2013-11-19 17:04:19 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 8 PJ 2013-12-05 18:34:20 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.