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.

Sign up for GitHub

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

Jump to bottom

Dyno PIDs on Heroku #35

Open
tooky opened this issue Nov 13, 2014 · 0 comments
Open

Dyno PIDs on Heroku #35

tooky opened this issue Nov 13, 2014 · 0 comments

Comments

@tooky
Copy link

tooky commented Nov 13, 2014

Am I right in thinking that oink uses the pid to evaluate changes in heap size?

Heroku logs come out looking some thing like:

Nov 12 16:06:16 app-name app/web.3: Nov 12 16:06:16 a2b85a63-8b2f-4779-bee5-3cc981238f23 rails[7]: Memory usage: 587724 | PID: 7 
Nov 12 16:06:37 app-name app/web.1: Nov 12 16:06:37 642db80d-23f8-4088-8ce4-4071bd0466ec rails[7]: Memory usage: 647864 | PID: 7

This is 2 dynos each running the process on the same PID, once we strip the heroku log information from the beginning we get:

Nov 12 16:06:16 a2b85a63-8b2f-4779-bee5-3cc981238f23 rails[7]: Memory usage: 587724 | PID: 7 
Nov 12 16:06:37 642db80d-23f8-4088-8ce4-4071bd0466ec rails[7]: Memory usage: 647864 | PID: 7

Will oink interpret those as being from the same process? Therefore recording that as a large heap increase?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tooky