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

Memory leak? #62

Open
crspybits opened this issue Feb 12, 2018 · 4 comments
Open

Memory leak? #62

crspybits opened this issue Feb 12, 2018 · 4 comments

Comments

@crspybits
Copy link
Owner

There was a warning on AWS on the prod instance of SyncServer-- with SharedImages. AWS also was claiming 90% memory utilization-- which seemed to have been the source of the warning. The warning has just gone away though. I'm not sure how to monitor the memory utilization of an EC2 instance.

@crspybits
Copy link
Owner Author

And today, this back again:

screen shot 2018-02-12 at 8 25 35 pm

@crspybits
Copy link
Owner Author

Here is a top run for the production server:

screen shot 2018-02-12 at 9 42 48 pm

@crspybits
Copy link
Owner Author

And here is a top run for the staging server, which had only been up for an hour or so and had few requests:

screen shot 2018-02-12 at 9 48 29 pm

@crspybits
Copy link
Owner Author

crspybits commented Feb 14, 2018

It seems vaguely possible that this issue could be coming from Kitura. Updating to the current Kitura wouldn't exactly test this, but if this is true, IBM could have resolved it.

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

No branches or pull requests

1 participant