Will this currently work on Heroku with multiple dynos?

[peteygao]

More specifically, will enabling this on Heroku across all dynos give a correct estimate of GC values based on data received from all running dynos, or would receiving potentially widely differing values request to request from different dynos throw off the tuner logic?

The use case I'm describing is having 30+ dynos (running Unicorn with 3 workers per dyno), each in various memory usage state, all sending samples to TuneMyGC. I'm wondering if the output of such a setup can be trusted?

[methodmissing]

@peteygao we have a Heroku addon in the works and can invite you as an alpha tester. Aggregations we didn't add to the MVP, but the agent already emits hostname, process id and parent process id for us to track and implement aggregation on the backend, when required We were waiting for a concrete context and problem to solve and work with for such a feature, especially on the Heroku platform. Willing to sync with us in private to get this rolled out over the next few days?

[charlietran]

@methodmissing i have a similar setup on Heroku and would love to be invited to the alpha

[jelder]

Is this the right place to ask for access to the Heroku alpha?

[ml]

I'd love to get an access to alpha!

[brega]

I would love to as well. Right place to request?

[erkki]

Coming soon, we'll keep you posted!

[pomartel]

I would also like an invite!

[methodmissing]

End of the week !! :-)

[beanieboi]

+1 :)

[BenMorganIO]

:+1:

[skyshard]

+1!

[methodmissing]

Hi all, ping your preferred Heroku emails for invites to the addon to tunemygc@bearmetal.eu . Thanks!

[fgrehm]

@methodmissing I'm having trouble with that email address :cry:

[methodmissing]

Haha, whoops, Thanks for flagging - tunemygc@bearmetal.eu - still to early for Bear Meal :-)