答复: Question about "Framework directly access Meso agent"

2016-02-17 Thread Suteng
Alex, We don't have test the performance of mesos. But we have develop a framework in house, which is like a simplified mesos, use to schedule a large number fine grain computation tasks. We find that master will be a bottleneck. One reason is our task contain several KB data, and task number

Re: Enable compiler optimization by default?

2016-02-17 Thread Klaus Ma
+1; So our CI will also update to use optimisation flags, right? We need to highlight this in upgrade document to our user; I used to meet so strange behaviour after changing -O level. On Thu, Feb 18, 2016 at 8:51 AM James DeFelice wrote: > +1 > On Feb 17, 2016 7:24

Re: Enable compiler optimization by default?

2016-02-17 Thread Avinash Sridharan
+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 wrote: > +1 > > Since the old days users are used to run > > ``` > configure

Re: Enable compiler optimization by default?

2016-02-17 Thread Neil Conway
On Wed, Feb 17, 2016 at 5:07 PM, Zameer Manji wrote: > Can't this problem also be solved by distributing packages that have > optimized binaries? The individuals/organizations that build packaged versions of Mesos should ensure that compiler optimizations are enabled -- but I

Re: Enable compiler optimization by default?

2016-02-17 Thread Zameer Manji
+1 Can't this problem also be solved by distributing packages that have optimized binaries? On Wed, Feb 17, 2016 at 4:56 PM, Alexander Rojas wrote: > +1 > > Since the old days users are used to run > > ``` > configure > make > sudo make install > ``` > > and things

Re: Enable compiler optimization by default?

2016-02-17 Thread Alexander Rojas
+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

Re: Enable compiler optimization by default?

2016-02-17 Thread James DeFelice
+1 On Feb 17, 2016 7:24 PM, "Neil Conway" 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)

Re: Enable compiler optimization by default?

2016-02-17 Thread Kevin Klues
+1 On Wed, Feb 17, 2016 at 4:24 PM, Neil Conway 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: >

Enable compiler optimization by default?

2016-02-17 Thread Neil Conway
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

Re: [VOTE] Release Apache Mesos 0.27.1 (rc1)

2016-02-17 Thread Jörg Schad
+ 1 (non-binding) Mac OS: non-root: DockerFetcherPluginTest.INTERNET_CURL_FetchManifest flaky, already tracked by MESOS-4570 root: ExamplesTest.JavaFramework failed tracked already by MESOS- 3582

Re: [VOTE] Release Apache Mesos 0.27.1 (rc1)

2016-02-17 Thread Zhitao Li
+1 (non binding) Debian 8 (jessie) plain non root OK. Mac OS X plain non root OK. Ubuntu 14.04 plain/SSL with root and docker-engine 1.10: Only flaky test I observed on Ubuntu 14.04 is HealthCheckTest.HealthStatusChange, which is tracked in MESOS-1802 already. > On Feb 17, 2016, at 5:21 AM,

Re: Contribution Request

2016-02-17 Thread Artem Harutyunyan
Done! Welcome to Mesos! On Wed, Feb 17, 2016 at 9:48 AM, Kevin Devroede wrote: > Hello, > > Can you please add me to the list of Mesos contributors? > > I would like to submit a code review for the following JIRA: > https://issues.apache.org/jira/browse/MESOS-4693 < >

Re: Question about "Framework directly access Meso agent"

2016-02-17 Thread Guangya Liu
For your concern of large scale cluster, there is indeed a JIRA tracking this https://issues.apache.org/jira/browse/MESOS-3548 Thanks, Guangya On Wed, Feb 17, 2016 at 12:14 PM, Suteng wrote: > Hi, > > > > Currently, Mesos framework’s task related operations lauchTask, >

Re: Question about "Framework directly access Meso agent"

2016-02-17 Thread Alex Rukletsov
Suteng— such optimization makes sense in certain cases (e.g. sending a framework message), but it can be rather tricky in general, because the master has to maintain bookkeeping. Moreover, with the upcoming HTTP API it becomes harder for a framework to determine where to send messages to reach a

Re: [VOTE] Release Apache Mesos 0.27.1 (rc1)

2016-02-17 Thread Bernd Mathiske
+1 (binding) Test failures look a lot like with 0.27.0. Not clean, but nothing deemed too drastic yet. CentOS 7 plain: FetcherCacheHttpTest.HttpCachedSerialized flaky again, filed MESOS-4692 LinuxFilesystemIsolatorTest.ROOT_ImageInVolumeWithRootFilesystem known as flaky: MESOS-4674

Re: Question about "Framework directly access Meso agent"

2016-02-17 Thread Guangya Liu
For your concern of large scale cluster, there is indeed a JIRA tracking this https://issues.apache.org/jira/browse/MESOS-3548 Thanks, Guangya On Wed, Feb 17, 2016 at 12:14 PM, Suteng wrote: > Hi, > > > > Currently, Mesos framework’s task related operations lauchTask, >

Contribution Request

2016-02-17 Thread Kevin Devroede
Hello, Can you please add me to the list of Mesos contributors? I would like to submit a code review for the following JIRA: https://issues.apache.org/jira/browse/MESOS-4693 Thanks, Kevin