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

[BUG] Issues with the HTTP logs segrep enabled, security enabled benchmark? #13052

Open
tronboto opened this issue Apr 3, 2024 · 1 comment
Labels
bug Something isn't working Indexing:Performance Performance This is for any performance related enhancements or bugs

Comments

@tronboto
Copy link

tronboto commented Apr 3, 2024

Describe the bug

The "HTTP logs - indexing throughput (Security enabled) - SegRep enabled" is:

  • Only run against arm64 and 2.13.0
  • Around 20% slower today than yesterday
  • Around 100x slower than the equivalent segrep enabled, security disabled benchmark

Related component

Indexing:Performance

To Reproduce

  1. Go to https://opensearch.org/benchmarks
  2. Inspect the "HTTP logs - indexing throughput (Security enabled) - SegRep enabled" chart

Expected behavior

Like the equivalent NYC taxis benchmark, I would expect to see all architectures and versions tested and the performance to be roughly similar to the benchmark with security enabled.

Additional Details

N/A

@peternied
Copy link
Member

[Triage - attendees 1 2 3 4 5 6 7 8]
@tronboto Thanks for filing this issue.

@bbarani Can you also look into this to see if we are tracking this appropriately or if this is about documentation the dashboard?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Indexing:Performance Performance This is for any performance related enhancements or bugs
Development

No branches or pull requests

2 participants