Skip to content

Performance regression in filters #141

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

Open
mgamanho opened this issue May 7, 2025 · 0 comments
Open

Performance regression in filters #141

mgamanho opened this issue May 7, 2025 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@mgamanho
Copy link
Contributor

mgamanho commented May 7, 2025

Describe the bug
Performance for filter-based calls is worse now in some cases than it was before moving to partitioned indices.

To Reproduce
Steps to reproduce the behaviour:
Measure time to query in large datasets.

Expected behaviour
Performance for queries should match or exceed that of pre index partitioning versions (14.1.1.0 or 12.2.1.4 currently still use monolithic index contents).

Environment (please complete the following information):

  • Coherence CE version (or Git SHA): 25.03
  • Java version and Java vendor: 21
  • OS: [e.g. iOS]: N/A
  • OS Version [e.g. 22]: N/A
  • Is this a container/cloud environment, e.g. Docker, CRI-O, Kubernetes, if so include additional information about the container environment, versions etc.: no
@mgamanho mgamanho added the bug Something isn't working label May 7, 2025
@mgamanho mgamanho self-assigned this May 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant