You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: