Correct way to enable Server GC in RC2?

[jeremymeng]

The migration guide suggests something like the following, which seems from aspnet/Announcements#175

{
  "runtimeOptions": {
    "gcServer": true,
    "gcConcurrent": true
  }
}

However, when I tried on RC2, it doesn't work for me. I had to use the code below

  "runtimeOptions": {
    "configProperties": {
      "System.GC.Server": true
    }
  }

[danroth27]

@ajaybhargavb @piotrpMSFT

Here is what I see in our RC2 templates:

  "runtimeOptions": {
    "gcServer": true
  }

When you say that the above doesn't work for you can you clarify what exactly you are seeing? How are you detecting whether server GC is being used?

[jeremymeng]

I have this code:

            if (GCSettings.IsServerGC)
            {
                Console.WriteLine("Server GC");
            }
            else
            {
                Console.WriteLine("Workstation GC");
            }

It prints out "Workstation GC" when I use gcServer": true

[jeremymeng]

A related issue: https://github.com/dotnet/cli/issues/2121
A related commit: aspnet/Benchmarks@b763266

[ajaybhargavb]

@danroth27, I think the structure of runtimeOptions has changed since the announcement. dotnet/aspnetcore#1418 (comment)

[danroth27]

@sayedihashimi @phenning @ajaybhargavb @piotrpMSFT @rachelappel So what we have in the templates for RC2 is incorrect? The JSON schema also appears to be incorrect:

[sayedihashimi]

The runtime team owns the schema, and I think it can be updated on the fly.

[danroth27]

@sayedihashimi @barrytang This is more than just a schema issue. It looks like what we have in our template project.json files is wrong.

[bragma]

I'm a bit lost. Is this valid also for webjobs (console apps) targeting net461?

[danroth27]

No, for console apps target the full .NET Framework you would need to enable server GC in app.config.