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

Performance benchmark for wildcard field type #358

Open
msfroh opened this issue Jul 29, 2024 · 0 comments
Open

Performance benchmark for wildcard field type #358

msfroh opened this issue Jul 29, 2024 · 0 comments
Assignees

Comments

@msfroh
Copy link

msfroh commented Jul 29, 2024

In 2.15, we added the wildcard field type that works well for cases where you want arbitrary substring matches (versus full-text search).

While we added unit tests and integration tests, we did not do any benchmarking. In particular, it would be nice to see how matches on arbitrary substrings on a wildcard field compare to similar queries on text/keyword field types. (Also, it would be interesting to see how much worse exact matches perform on wildcard fields versus text/keyword.)

We should be able to add wildcard fields to the http_logs and Big5 workloads. (It's extra indexing work, so we need to keep in mind that indexing numbers will get worse.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Now (This Quarter)
Development

No branches or pull requests

3 participants