Skip to content

[Inductor] Track deterministic alloc_id assignment across cached compilation artifacts #172475

@eee4017

Description

@eee4017

🚀 The feature, motivation and pitch

Description

Currently, alloc_id is required to be unique per allocation site within a process lifetime, so that:

  • All ranks use consistent memory addresses for a given collective
  • Expensive P2P memory registration (e.g. ncclCommWindowRegister) can be skipped on subsequent uses via cached pointers

In the current implementation, we generate alloc_id via random.

f"alloc_id={random.randint(0, 2**64 - 1)})"

Proposed Direction

#171909 (comment)

Related Context

Alternatives

No response

Additional context

No response

cc @mruberry @kurtamohler @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @kadeng @muchulee8 @amjames @aakhundov @coconutruben @jataylo

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureA request for a proper, new feature.module: determinismmodule: inductoroncall: pt2triagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate module

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions