Skip to content

optimizer: emit an inspectable trace across extraction, candidates, and assignments #774

Closed as not planned

Description

@milindsrivastava1997

Goal

Provide an inspectable, machine-readable optimizer trace rather than relying on verbose logs alone.

Change

Add an option such as --optimizer-trace-json <path> that emits stage-tagged JSON for:

  1. RQEs
  2. extracted QueryRequirements
  3. OptimizerItems (requirements, T, SLAs, frequency)
  4. generated structural candidates per item
  5. eligible (item, config) edges after active filters
  6. selected deployments and item assignments

Keep normal debug! logs concise: stage counts and stable identifiers, with the trace artifact holding full details.

Integration

Part of #753.

Activity

  1. milindsrivastava1997 commented on Oct 27, 2026

    @milindsrivastava1997
    ContributorAuthor

    Superseded by the rqe-optimizer MILP path (#790, ProjectASAP/sketch-bench#129, #794); the greedy optimizer was removed in #807. The greedy stages listed here no longer exist; re-file against rqe-optimizer if a trace is still wanted.

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions