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

Monotonically Increasing CPU usage for redis proxy #664

Open
tomzilla opened this issue Feb 24, 2022 · 3 comments
Open

Monotonically Increasing CPU usage for redis proxy #664

tomzilla opened this issue Feb 24, 2022 · 3 comments

Comments

@tomzilla
Copy link

Hello

I'm seeing this pattern of increasing CPU usage over time. This is a staging environment and has pretty low traffic. Memory usage was also increasing like this before I set the -m 512 flag. Now memory usage seems to be stable.

We are running mostly HSET and HGET commands within Lua scripts.

First time running twemproxy. Not sure what to expect here.
image

@tomzilla tomzilla reopened this Feb 24, 2022
@TysonAndre
Copy link
Collaborator

TysonAndre commented Feb 25, 2022

What OS is this?

What version are you running? Does this happen with the latest release?

What config options are you using for the redis pool?

I don't remember seeing any similar bug reports and have used redis before without issues with 0.5.0.

Do the sylogs say anything interesting, e.g. frequent disconnections? (See help message for how to log)

@TysonAndre TysonAndre changed the title Monotonically Increasing CPU usage Monotonically Increasing CPU usage for redis proxy Feb 25, 2022
@TysonAndre
Copy link
Collaborator

Memory usage was also increasing like this before I set the -m 512 flag. Now memory usage seems to be stable.

Currently, twemproxy maintains a free list manually, and doesn't release memory (e.g. if there are spikes in latencies). This is a problem I've seen before - I was considering an approach to free values in batches periodically in a future releases.

@TysonAndre
Copy link
Collaborator

See #553 for memory

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

No branches or pull requests

2 participants