arrow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Zhe Zhang <zhe.zhang.resea...@gmail.com>
Subject Re: Question about mutability
Date Wed, 24 Feb 2016 19:24:27 GMT
Well I could be wrong. I'm new to the codebase myself. Let's hope someone
from the core dev team can help clarify.

On Wed, Feb 24, 2016 at 11:20 AM Michael D. Coon <mdcoon1@yahoo.com.invalid>
wrote:

> I had the same understanding as Corey and thought that apps shared an
> allocated memory space for the sole purpose of eliminating the need to copy
> data between the apps. If it's just a replacement for protobuf SERDE, that
> makes it a whole lot less exciting :(
>
>
>
>     On Wednesday, February 24, 2016 2:17 PM, Andrew Brust <
> andrew.brust@bluebadgeinsights.com> wrote:
>
>
>  Hmm...that's not exactly how Jaques described things to me when he
> briefed me on Arrow ahead of the announcement.
>
> -----Original Message-----
> From: Zhe Zhang [mailto:zhz@apache.org]
> Sent: Wednesday, February 24, 2016 2:08 PM
> To: dev@arrow.apache.org
> Subject: Re: Question about mutability
>
> I don't think one application/process's memory space will be made
> available to other applications/processes. It's fundamentally hard for
> processes to share their address spaces.
>
> IIUC, with Arrow, when application A shares data with application B, the
> data is still duplicated in the memory spaces of A and B. It's just that
> data serialization/deserialization are much faster with Arrow (compared
> with Protobuf).
>
> On Wed, Feb 24, 2016 at 10:40 AM Corey Nolet <cjnolet@gmail.com> wrote:
>
> > Forgive me if this question seems ill-informed. I just started looking
> > at Arrow yesterday. I looked around the github a tad.
> >
> > Are you expecting the memory space held by one application to be
> > mutable by that application and made available to all applications
> > trying to read the memory space?
> >
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message