Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for more than 64 logical processors (process groups) #57

Open
rpaquay opened this issue Feb 10, 2020 · 1 comment
Open

Add support for more than 64 logical processors (process groups) #57

rpaquay opened this issue Feb 10, 2020 · 1 comment

Comments

@rpaquay
Copy link
Contributor

rpaquay commented Feb 10, 2020

As a .NET app, the VsChromium server process will only use one process group by default. This limits the # of cores to 64 maximum.

According to https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/thread-useallcpugroups-element, a simple change to the app.config file enables support for more than 64 logical processors:

app.config

<configuration>
   <runtime>
      <Thread_UseAllCpuGroups enabled="true"/>
      <GCCpuGroup enabled="true"/>
      <gcServer enabled="true"/>
   </runtime>
</configuration>
@rpaquay
Copy link
Contributor Author

rpaquay commented Feb 10, 2020

Note: Unfortunately, things are not as simple. After adding the app.config file shown in the #57, the VsChromium server memory usage grew by almost 20% on a 72 Core machine (192GB RAM).

When loading a project with more than 1,500,000 files, memory usage (Working Set and Commit size) grew by 1.2GB and 2.2GB respectively.

Before:

  • Before
    • Working set: 8,215 MB
    • Commit size: 8,322 MB
  • After
    • Working set: 9,457 MB (+1.2 GB)
    • Commit size: 10,589 MB (+2.2 GB)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant