Skip to content

Graviton (m7g.4xlarge) validation of thread-per-core serving before release #902

Description

@membphis

Split out of #891 (thread-per-core workers), which names this run as the release gate.

Every published number for the thread-per-core mode comes from a 12-vCPU x86 VM, where virtualized context-switch cost amplifies the win. The gain should be smaller on bare metal, and ARM is the deployment target that motivated the work.

Gate: run the #891 A/B (both proxy.thread_per_core legs, c=16/32/128 and the 10ms-TTFT high-concurrency point, fail=0) on an m7g.4xlarge against the merged branch.

If thread-per-core does not win there, flipping the Linux platform default back is a one-line change with no other code impact — that rollback decision is what this issue exists to make deliberately.

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