Skip to content

perf: GKR - Caching Evaluation point Eq tables #1723

Description

@Tabaie

When different wires/batches receive an evaluation claim at the same point, it makes sense to precompute the eq table at that point just once and clone/use it where needed. There are some nuances:

  1. This has a cost in memory allocations
  2. The cost of computing an eq table is one multiplication pass. If the cached claim is being folded along others, it only saves operations if it constitutes the first claim (folding coefficient $r^0=1$)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    feat: gkrPRs related to GKR

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions