Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Constraint Level Latency Measurement #2397

Closed
2 tasks
acpana opened this issue Nov 9, 2022 · 2 comments
Closed
2 tasks

Constraint Level Latency Measurement #2397

acpana opened this issue Nov 9, 2022 · 2 comments
Labels

Comments

@acpana
Copy link
Contributor

acpana commented Nov 9, 2022

This is a tracking issue for offering a per constraint measurement of the evaluation latency, i.e. how long the call to constraint framework's client .Review() took.

There are two phases:

  • Phase 1: changes needed for measuring batched/ sharded constraints
  • Phase 2: changes needed to reduce the batch size to 1

Phase 1:

Phase 2:

  • TODO; jotting down thoughts:
    • expose constraint framework option to evaluate constraints individually (or by a certain max batch size)
    • expose constraint framework option above thru the gatekeeper config
@stale
Copy link

stale bot commented Jan 9, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jan 9, 2023
@maxsmythe maxsmythe removed the stale label Jan 10, 2023
@stale
Copy link

stale bot commented Mar 11, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Mar 11, 2023
@stale stale bot closed this as completed Mar 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants