-
Notifications
You must be signed in to change notification settings - Fork 444
bench: Initial wasm benchmarks #790
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @simar7 I left a few comments but the main thing is to see if we can use opa.Target option instead of github.com/open-policy-agent/golang-opa-wasm module. By doing that we could benchmark same Rego rules with different targets (rego vs wasm)
Signed-off-by: Simar <simar@linux.com>
Signed-off-by: Simar <simar@linux.com>
Signed-off-by: Simar <simar@linux.com>
Signed-off-by: Simar <simar@linux.com>
Signed-off-by: Simar <simar@linux.com>
Signed-off-by: Simar <simar@linux.com>
Signed-off-by: Simar <simar@linux.com>
…tests Signed-off-by: Simar <simar@linux.com>
Signed-off-by: Simar <simar@linux.com>
Signed-off-by: Simar <simar@linux.com>
I cleaned up and refactored tests as per feedback. Now we have table driven tests for each type along with subtests.
|
I also left some remarks on this PR: #796 regarding memory profile for WASM #796 (comment) and CPU profile #796 (comment) |
Signed-off-by: Daniel Pacak <pacak.daniel@gmail.com>
Signed-off-by: Simar simar@linux.com