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

Free performance data when ExportObject is released #5480

Merged
merged 1 commit into from
May 16, 2024

Conversation

niloc132
Copy link
Member

Cuts leaked memory from released objects by around 50%.

Partial #5479

Cuts leaked memory from released objects by around 50%.

Partial deephaven#5479
@niloc132 niloc132 added the grpc label May 10, 2024
@niloc132 niloc132 added this to the 3. May 2024 milestone May 10, 2024
@@ -1141,6 +1141,7 @@ protected synchronized void destroy() {
if (!(caughtException instanceof StatusRuntimeException)) {
caughtException = null;
}
queryPerformanceRecorder = null;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the goal here? I assume we're not keeping hard refs to the ExportObject once it's destroyed most of the time, anyway.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At this time, we do keep hard refs to ExportObjects within a session so that we can tell if an unrecognized export ID is either stale RELEASED ("sorry, you raced but you just missed it, that was already released") or UNKNOWN ("hmm, never seen that before, you probably raced it and won, so we'll wait until it appears").

The linked issue mentions a strategy to handle this, with a RowSet for known-released objects, so that we no longer need to keep the ExportObject itself around.

@niloc132 niloc132 merged commit cdd0e08 into deephaven:main May 16, 2024
16 of 21 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators May 16, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants