Skip to content

Conversation

@luciaquirke
Copy link
Collaborator

More VRAM efficient variant where preconditioners can be spread across an arbitrary number of nodes to compute large outer products. This is useful because preconditioners are often applied to a query and then the query is run across a large dataset, so slow but VRAM-efficient preconditioner computation and usage is a scalable pattern.

Because the preconditioners don't necessarily fit on a single GPU we use GLOO to do distributed CPU operations.

@luciaquirke luciaquirke changed the title [Option] Parallelize preconditioners across ranks #94 [Option] Parallelize preconditioners across ranks Dec 19, 2025
@luciaquirke luciaquirke changed the title [Option] Parallelize preconditioners across ranks [Option] Parallelize preconditioners across ranks; multi-node FSDP Dec 21, 2025


@dataclass(kw_only=True)
class MultiNodeGradientCollector(HookCollectorBase):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this going to be a replacement for GradientCollector? It seems like we don't it, if we have this one

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I will merge this as a separate class for dogfooding and then replace the GradientCollector when we're convinced it's stable


def build_worker(
rank: int,
local_rank: int,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add to doc what this does

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

Successfully merging this pull request may close these issues.

3 participants