Bug 8557 - Default value for TaskScheduler.MaximumConcurrencyLevel different between MS.NET and Mono
Summary: Default value for TaskScheduler.MaximumConcurrencyLevel different between MS....
Alias: None
Product: Class Libraries
Classification: Mono
Component: mscorlib ()
Version: 2.10.x
Hardware: PC Linux
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2012-11-22 10:54 UTC by Karol Gwaj
Modified: 2012-11-23 06:42 UTC (History)
2 users (show)

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

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.

Related Links:

Description Karol Gwaj 2012-11-22 10:54:47 UTC
Looks like default value for TaskScheduler.MaximumConcurrencyLevel is different between MS.NET and Mono:
MONO: TaskScheduler.MaximumConcurrencyLevel == <processors count>
MS.NET: TaskScheduler.MaximumConcurrencyLevel == int.MaxValue

it is making difference, because Mono methods on Parallel class (ForEach, Invoke, ...) in some cases execute much slower than in MS.NET (if you specify parallelizm level greater than number of processors)
Comment 1 Marek Safar 2012-11-23 06:42:53 UTC
Fixed in master