cube icon indicating copy to clipboard operation
cube copied to clipboard

Cubejs server is not releasing memory

Open ifokeev opened this issue 3 years ago • 3 comments

Describe the bug Cubejs is not releasing the memory because of some internal cache mechanics. I tried local/redis queues and it's pretty the same. Redis is not releasing the memory too (I gave cubejs own Redis server).

To Reproduce Query the data all the time and work with cubejs quering big datasets (50K+ rows)

Expected behavior I'm expecting releasing of the memory after the query/data expired

Version: 0.26.60

Additional context May be related https://github.com/cube-js/cube.js/issues/2333

ifokeev avatar Jul 02 '21 20:07 ifokeev

Hi @ifokeev :wave:

Could you try updating to the latest version (v0.27.46 at time of writing)? Thanks in advance 😀

hassankhan avatar Jul 03 '21 20:07 hassankhan

Hi, any update for this?

I am using 0.29.37, but memory still not release.

image

guangzh3n avatar May 11 '22 05:05 guangzh3n

👋 a quick reminder that we will be replacing Redis with Cube Store as announced in this blog post.

rpaik avatar Jul 28 '22 05:07 rpaik

Is it solved when we set the Cube to use the Cube Store? During my tests I can see that the memory still increasing over time even if I set Cube to work with Cube Store and an external Redis.

hiratab avatar Sep 27 '22 17:09 hiratab

@guangzh3n @hiratab By default Node.js won't be releasing most of RSS memory back to the operating system once allocated. So it'd usually be normal behavior. Are you experiencing any OOM because of that? If so, please feel free to reproduce it in Cube Cloud https://cubecloud.dev/auth/signup. This will allow our engineering team to snapshot Cube memory in an environment precisely tweaked for production usage to see if there're memory leaks.

paveltiunov avatar Sep 27 '22 21:09 paveltiunov