Hi Sean, > Personally, I would leave this off. Is this not production ready, thus we should disable it?
Thanks, Liming ________________________________________ From: Sean Owen <so...@cloudera.com> Sent: Saturday, February 13, 2016 2:18 AM To: Ovidiu-Cristian MARCU Cc: Ted Yu; Sea; user@spark.apache.org Subject: Re: off-heap certain operations I don't think much more is said since in fact it would affect parts of the implementations of lots of operations -- anything touching Tungsten. It wouldn't be meaningful to try to list everything. The difference is allocating memory on the heap or with sun.misc.Unsafe. This is definitely something you'd need to be a developer to know whether to use, and if you're a developer and curious, you can just grep the code for this flag, and/or read into what Tungsten does. Personally, I would leave this off. On Fri, Feb 12, 2016 at 6:10 PM, Ovidiu-Cristian MARCU <ovidiu-cristian.ma...@inria.fr> wrote: > I found nothing about the certain operations. Still not clear, certain is > poor documentation. Can someone give an answer so I can consider using this > new release? > spark.memory.offHeap.enabled > > If true, Spark will attempt to use off-heap memory for certain operations. > > On 12 Feb 2016, at 13:21, Ted Yu <yuzhih...@gmail.com> wrote: > > SP > > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@spark.apache.org For additional commands, e-mail: user-h...@spark.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@spark.apache.org For additional commands, e-mail: user-h...@spark.apache.org
