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

IndexReader GC Performance Issue #950

Open
1 task done
stesee opened this issue Jun 24, 2024 · 0 comments · May be fixed by #951
Open
1 task done

IndexReader GC Performance Issue #950

stesee opened this issue Jun 24, 2024 · 0 comments · May be fixed by #951
Labels

Comments

@stesee
Copy link

stesee commented Jun 24, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

After a large number of queries, our solution becomes terribly slow and never recovers. One core remains at 100% load.

The profiler indicates that the issue seems to be in the finalizer of IndexReader.
image

Expected Behavior

IndexReader should perform reliable

Steps To Reproduce

The issue is reproducible using confidential data and disappears when dropping the finalizer without drawbacks. Please read the recommendations around the usage of finalizers: Understanding When to Use a Finalizer in Your .NET Class. By the way, Dispose(false) seems to interact with managed objects, which could also be contributing to the problem.

Exceptions (if any)

No response

Lucene.NET Version

4.8.0-beta00016

.NET Version

.net 4.8

Operating System

Windows

Anything else?

No response

@stesee stesee added the is:bug label Jun 24, 2024
@stesee stesee changed the title IndexSearcher GC Performance Issue IndexReader GC Performance Issue Jun 24, 2024
@stesee stesee linked a pull request Jun 25, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant