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

ram: high traffic sites appear to have memory leak #464

Open
stephen-soltesz opened this issue Jul 15, 2020 · 4 comments
Open

ram: high traffic sites appear to have memory leak #464

stephen-soltesz opened this issue Jul 15, 2020 · 4 comments

Comments

@stephen-soltesz
Copy link
Contributor

Watching the topk dashboard, I noticed that very high traffic sites, maa.. mnl.., appear to have a gradual memory leak for all sidecar services that is not observed at other sites.

Screen Shot 2020-07-15 at 7 29 22 AM

Image include reset during rollout on 07/08

@stephen-soltesz stephen-soltesz transferred this issue from m-lab/ndt-server Jul 15, 2020
@nkinkade
Copy link
Contributor

There may indeed be a memory leak, but one other factor probably contributing to the unusually high load at MAA01, is that MAA02 has been down for the past couple weeks, meaning that MAA01 has to carry the whole load for that region.

@stephen-soltesz
Copy link
Contributor Author

gru is also one of our busiest metros. If there is a leak, it seems more likely to be triggered in busy locations. It's possible the leak is very slow at other locations.

@laiyi-ohlsen
Copy link

@stephen-soltesz

@stephen-soltesz
Copy link
Contributor Author

There is a growth curve. It's possible the curve is leveling off as it approaches 1GB to 1.5GB?

The highest memory users are:

  • tcp-info
  • traceroute-caller

Screen Shot 2020-08-10 at 3 01 42 PM

This requires pprof heap traces to investigate further. It may also require running a service for longer than 30days.

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