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

High memory usage #170

Closed
Maronato opened this issue Oct 9, 2020 · 4 comments
Closed

High memory usage #170

Maronato opened this issue Oct 9, 2020 · 4 comments

Comments

@Maronato
Copy link

Maronato commented Oct 9, 2020

Hello! First of all, thank you for creating Ackee. Such a beautiful tool and a breeze to install :)

That said, it seems to be consuming an unusually high amount of memory for a node app. A single instance is taking an average of 170mb just to exist, with next to no traffic running into it. My other node apps consume about half as much memory. In fact, Ackee is currently the third most memory-hungry app running on my cluster with 30+ services.

I'm running version 2.0.0.

Below are the stats of the last 24 hours for a single container running Ackee. CPU and network are ok and, as you can see, it received next to no traffic over this period.

The spike in usage at the end represents the moment I logged into it to confirm the current version.

CleanShot 2020-10-09 at 13 45 42@2x
CleanShot 2020-10-09 at 13 53 28@2x
CleanShot 2020-10-09 at 13 51 39@2x
CleanShot 2020-10-09 at 14 11 57@2x

@electerious
Copy link
Owner

Thanks for letting me know. It would be interesting to see what causes this high usage.

Will it stay at ~150mb or does the memory usage grow?

@BetaHuhn
Copy link
Contributor

I have also noticed that Ackee recently started consuming a lot more memory than before. I don't know since when. I am running v2 for a few weeks now and don't think it was this high when I upgraded but I am not 100% sure. It currently consumes around 100 - 150 mb.

@electerious
Copy link
Owner

It looks like that the feature/serverless branch uses a lot less memory. This could be because I'm now building the source files in a different step, instead of requiring all build files (babel, sass, etc.) in the server. They could unnecessary fill the memory even when they're only used once. From ~126mb to ~50mb.

@electerious
Copy link
Owner

The serverless branch has been merged into develop and will be part of the next release. Please let me know when the usage is still high.

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

3 participants