This is Xamarin's bug tracking system. For product support, please use the support links listed in your Xamarin Account.
Bug 8557 - Default value for TaskScheduler.MaximumConcurrencyLevel different between MS.NET and Mono
Summary: Default value for TaskScheduler.MaximumConcurrencyLevel different between MS....
Status: RESOLVED FIXED
Alias: None
Product: Class Libraries
Classification: Mono
Component: CORLIB (show other bugs)
Version: 2.10.x
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-11-22 10:54 UTC by Karol Gwaj
Modified: 2012-11-23 06:42 UTC (History)
2 users (show)

See Also:
Tags:


Attachments

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

Note You need to log in before you can comment on or make changes to this bug.