We are working with Mesos folks to resolve it. There is a Mesos performance working group that folks can join if they'd like to contribute: http://mesos.apache.org/blog/performance-working-group-progress-report/
I'm not sure what you mean by branch. Everything we used to scale test is on master. On Mon, Jan 15, 2018 at 10:08 AM, Meghdoot bhattacharya < [email protected]> wrote: > David, should twitter try against mesos 1.5 to see if things are better > with the new api instead of libmesos. This is going to be a drift over time > that will stop us from adopting new features. > > If it was sometime back it would be good to rerun the tests and open a > ticket in Mesos if issues exist. All aurora users can then push for > resolution. > > Also details on branch etc that has the api integration? > > Thx > > On Jan 12, 2018, at 11:39 AM, David McLaughlin <[email protected]> > wrote: > > I'm not sure I agree with the summary. Bill's proposal was using shutdown > only when using the new API. I would also support this if it's possible. > > On Fri, Jan 12, 2018 at 11:14 AM, Mohit Jaggi <[email protected]> > wrote: > >> Summary so far: >> - Bill supports making this change >> - This change cannot be made in a backward compatible manner >> - David (Twitter) does not want to use HTTP APIs due to performance >> concerns. I conclude that folks from Twitter don't support this change >> >> Question: >> - Are there other users that want this change? >> >> >> >
