Thanks Zhitao and Anand! I've been looking forward to using arena
allocation to improve performance.
On Fri, May 26, 2017 at 6:01 PM, Qian Zhang wrote:
> Thanks Anand and Zhitao!
>
> So I think we can remove the code like below, and switch to use the native
> maps supported
Thanks Anand and Zhitao!
So I think we can remove the code like below, and switch to use the native
maps supported by proto3, right?
https://github.com/apache/mesos/blob/master/include/mesos/docker/v1.proto#L25:L28
And just curious, if we use the proto2 syntax in each .proto files in
Mesos, is
Thanks Anand and Zhitao!
On Fri, May 26, 2017 at 3:40 PM Anand Mazumdar wrote:
> We recently committed this [1] and it would be part of the *next major
> release* (1.4.0). Also, we upgraded to the newer protobuf release 3.3.0.
>
> For Mesos developers, this means that we can
We recently committed this [1] and it would be part of the *next major
release* (1.4.0). Also, we upgraded to the newer protobuf release 3.3.0.
For Mesos developers, this means that we can use proto3 features like arena
allocation [2], maps [3] etc. Note that we still need to use the proto2
+ dev
Bumping up the thread to ensure it's not missed.
-anand
On Tue, Apr 25, 2017 at 11:01 AM, Zhitao Li wrote:
> Dear framework owners and users,
>
> We are working on upgrading the protobuf library in Mesos to 3.2.0 in
>
Dear framework owners and users,
We are working on upgrading the protobuf library in Mesos to 3.2.0 in
https://issues.apache.org/jira/browse/MESOS-7228, to overcome some protobuf
limitation on message size as well as preparing for further improvement. We
aim to release this with the upcoming
6 matches
Mail list logo