Re:Heroku Blog: Routing Performance Update
by btilly on Saturday February 16, 2013 @01:10PM
(#5232360)
It is quite possible to know that the mesh is not exactly as documented without having realized that the difference has a severe performance impact.
Re:Heroku Blog: Routing Performance Update
by azarias on Saturday February 16, 2013 @04:04PM
(#5233026)
I think they also addressed the performance issue in addition to saying it is not documented: "...evolving away from the global backlog concept in order to provide better support for different concurrency models"
Re:Heroku Blog: Routing Performance Update
by btilly on Sunday February 17, 2013 @01:15AM
(#5234374)
The fact that a year later, performance for their starting use case had not been addressed says that they failed to address the performance issue.
It is still not clear to me that they actually really understood the performance issue, or how big it was going to be.
Heroku's blog response: "but until this week, we failed to see a common thread among these reports."
vs.
Adam's response to Tim Watson, a year ago:
"You're correct, the routing mesh does not behave in quite the way described by the docs. We're working on evolving away from the global backlog concept in order to provide better support for different concurrency models, and the docs are no longer accurate. The current behavior is not ideal, but we're on our way to a new model which we'll document fully once it's done."
https://groups.google.com/forum/?fromgroups=#!msg/heroku/8eO...