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 GitHub or Developer Community 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.
using System; using System.Threading; using System.Diagnostics; class MyContext { public static void Main () { int counter = 0; const int iter = 10000000; var sw = new Stopwatch (); sw.Start (); for (int i = 0; i < iter; ++i) { ThreadPool.QueueUserWorkItem (delegate { Interlocked.Increment (ref counter); }); } Console.WriteLine (sw.ElapsedMilliseconds); SpinWait.SpinUntil (() => counter == iter); Console.WriteLine (sw.ElapsedMilliseconds); } } Mono on amd64 8 cores 11043 17404 .NET on amd64 4 cores 3317 3319
The different with .NET is big, but if you compare it to mono 2.6, we are 10-15x faster... The problem with this kind of micro test is the way we store the work items, which involves dynamically allocating lists of arrays that are managed by the GC. I have no idea of what to do next.
One option would be to not allocate System.Runtime.Remoting.Messaging.AsyncResult or reduce its size if the allocation cannot be avoided
We use the same TP as dotnet now.