+1 Since most of our debugging is using logs rather than GDB, don't see the point of not having these optimization flags turned on by default.
On Wed, Feb 17, 2016 at 4:56 PM, Alexander Rojas <[email protected]> wrote: > +1 > > Since the old days users are used to run > > ``` > configure > make > sudo make install > ``` > > and things just work. With the model we have, we are just encouraging > users to run their data centers with unoptimized versions of Mesos, which > just hurts their performance. > > > > On 17 Feb 2016, at 16:24, Neil Conway <[email protected]> wrote: > > > > Hi folks, > > > > At present, Mesos defaults to compiling with "-O0"; to enable compiler > > optimizations, the user needs to specify "--enable-optimize". > > > > I'd like to propose we change the default, for a few reasons: > > > > (1) The autoconf default for CFLAGS/CXXFLAGS is "-O2 -g". Anecdotally, > > I think most software packages compile with a reasonable level of > > optimizations enabled by default. > > > > (2) I think we should make the default configure flags appropriate for > > end-users (rather than Mesos developers): developers will be familiar > > enough with Mesos to tune the configure flags according to their own > > preferences. > > > > (3) The performance consequences of not enabling compiler > > optimizations can be pretty severe: 5x in a benchmark I just ran, and > > we've seen between 2x and 30x (!) performance differences for some > > real-world workloads. > > > > Neil > > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245
