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?
Am I right in thinking that oink uses the pid to evaluate changes in heap size?
Heroku logs come out looking some thing like:
This is 2 dynos each running the process on the same PID, once we strip the heroku log information from the beginning we get:
Will oink interpret those as being from the same process? Therefore recording that as a large heap increase?