Skip to content

Fix memory leakage in kit.PayloadUnaryServerInterceptor#501

Merged
johanbrandhorst merged 2 commits intogrpc-ecosystem:masterfrom
tabby-ai:issue-498-kit-interceptor-memleak
Jul 14, 2022
Merged

Fix memory leakage in kit.PayloadUnaryServerInterceptor#501
johanbrandhorst merged 2 commits intogrpc-ecosystem:masterfrom
tabby-ai:issue-498-kit-interceptor-memleak

Conversation

@r3code
Copy link
Copy Markdown
Contributor

@r3code r3code commented Jul 12, 2022

Closes issue #498

A wrong assign creates multiple object for GC, and with every call appends new objects, so GC have to walk through thousands of objects. This causes high increasing memory and CPU usage. We saw in our services that it leads to CPU throttling and increasing of a memory usage.

Closes issue grpc-ecosystem#498

A wrong assign creates multiple object for GC, and with every call appends new objects, so GC have to walk through thousands of objects. This causes high increasing memory and CPU usage. We saw in our services that it leads to CPU throttling and increasing of a memory usage.
@google-cla
Copy link
Copy Markdown

google-cla Bot commented Jul 12, 2022

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@johanbrandhorst johanbrandhorst merged commit 7fdae0e into grpc-ecosystem:master Jul 14, 2022
@johanbrandhorst
Copy link
Copy Markdown
Collaborator

Thank you for this contribution!

@karelbilek
Copy link
Copy Markdown

OMG this hit me hard! Can you please put this to stable branch!!?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants