Skip to content

Optimizations when Environment.ProcessorCount > 1 in Kubernetes environment #11180

@tylerohlsen

Description

@tylerohlsen

I've noticed that our pods on a Kubernetes/Docker cluster with millicpu allocations all report Environment.ProcessorCount = 1.

Does the .Net Core CLR have any optimizations when Environment.ProcessorCount > 1 that we are missing out on or is anything is disabled or degraded when Environment.ProcessorCount = 1?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions