One of the problems we saw from this was that aurora doesn’t seem include the thermos overhead when computing allocated resources, so we were seeing a huge gap between what aurora said we were reserving and what mesos said was available. Perhaps the aurora UI should take the thermos executor overhead into account when computing used resources.
> On Sep 7, 2016, at 4:17 PM, Joshua Cohen <[email protected]> wrote: > > We run internally with -thermos_executor_cpu set to 0 (requiring task owners > to account for any executor CPU usage). This is generally safe, but task > owners should be notified that there's an outside chance they might see CPU > throttling that they were not previously seeing (assuming you're using > cgroup/cpu isolation that is). > > On Wed, Sep 7, 2016 at 2:44 PM, Wesley Chow <[email protected] > <mailto:[email protected]>> wrote: > It’s currently set to a default of 0.25, which seems excessive to us since we > tend to run a larger number of small tasks. Is bringing that down to 0.1 a > terrible thing to do? > > Thanks, > Wes > >
signature.asc
Description: Message signed with OpenPGP using GPGMail
