Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.programming > #8974 > unrolled thread

.NET and Processor Groups

Started byRobert Wessel <robertwessel2@yahoo.com>
First post2018-07-09 00:27 -0500
Last post2018-07-09 08:59 -0400
Articles 3 — 2 participants

Back to article view | Back to comp.programming


Contents

  .NET and Processor Groups Robert Wessel <robertwessel2@yahoo.com> - 2018-07-09 00:27 -0500
    Re: .NET and Processor Groups Sky89 <Sky89@sky68.com> - 2018-07-09 07:24 -0400
      Re: .NET and Processor Groups Sky89 <Sky89@sky68.com> - 2018-07-09 08:59 -0400

#8974 — .NET and Processor Groups

FromRobert Wessel <robertwessel2@yahoo.com>
Date2018-07-09 00:27 -0500
Subject.NET and Processor Groups
Message-ID<v3s5kd904kbdlhgbqu3fp5br00j4oshg7d@4ax.com>
Someone in my killfile posed some incorrect information about .NET and
processor groups on large Windows systems.  I saw that post as part of
someone else's reply.

Namely, it *is* possible for a .NET application (at least since v4.5
or so), to schedule threads on multiple processor groups, and thus not
be limited to the maximum of 64 threads that be in a single processor
group.

It is a feature that needs to be enabled.  Details at:

https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/thread-useallcpugroups-element

[toc] | [next] | [standalone]


#8975

FromSky89 <Sky89@sky68.com>
Date2018-07-09 07:24 -0400
Message-ID<phvgl9$rs6$1@dont-email.me>
In reply to#8974
On 7/9/2018 1:27 AM, Robert Wessel wrote:
> Someone in my killfile posed some incorrect information about .NET and
> processor groups on large Windows systems.  I saw that post as part of
> someone else's reply.
> 
> Namely, it *is* possible for a .NET application (at least since v4.5
> or so), to schedule threads on multiple processor groups, and thus not
> be limited to the maximum of 64 threads that be in a single processor
> group.
> 
> It is a feature that needs to be enabled.  Details at:
> 
> https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/thread-useallcpugroups-element
> 


I have tested it under Mono and it is not supported under Mono.



Thank you,
Amine Moulay Ramdane.

[toc] | [prev] | [next] | [standalone]


#8976

FromSky89 <Sky89@sky68.com>
Date2018-07-09 08:59 -0400
Message-ID<phvm8c$uhv$1@dont-email.me>
In reply to#8975
On 7/9/2018 7:24 AM, Sky89 wrote:
> On 7/9/2018 1:27 AM, Robert Wessel wrote:
>> Someone in my killfile posed some incorrect information about .NET and
>> processor groups on large Windows systems.  I saw that post as part of
>> someone else's reply.
>>
>> Namely, it *is* possible for a .NET application (at least since v4.5
>> or so), to schedule threads on multiple processor groups, and thus not
>> be limited to the maximum of 64 threads that be in a single processor
>> group.
>>
>> It is a feature that needs to be enabled.  Details at:
>>
>> https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/thread-useallcpugroups-element 
>>
>>
> 
> 
> I have tested it under Mono and it is not supported under Mono.
> 
> 
> 
> Thank you,
> Amine Moulay Ramdane.


Hello,

Sorry , it is working with Mono, here is the configuration file that i 
am using:



<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <runtime>
       <Thread_UseAllCpuGroups enabled="true"/>
       <GCCpuGroup enabled="true"/>
       <gcServer enabled="true"/>
    </runtime>
</configuration>




Thank you,
Amine Moulay Ramdane.

[toc] | [prev] | [standalone]


Back to top | Article view | comp.programming


csiph-web