I haven't touched Tungsten, but have proposed removing the deprecated old memory manager and settings -- yes I think that's the primary argument for it. https://github.com/apache/spark/pull/23457
On Wed, Jan 9, 2019 at 6:06 PM Erik Erlandson <eerla...@redhat.com> wrote: > Removing the user facing config seems like a good idea from the standpoint > of reducing cognitive load, and documentation > > On Fri, Jan 4, 2019 at 7:03 AM Sean Owen <sro...@apache.org> wrote: > >> OK, maybe leave in tungsten for 3.0. >> I did a quick check, and removing StaticMemoryManager saves a few hundred >> lines. It's used in MemoryStore tests internally though, and not a trivial >> change to remove it. It's also used directly in HashedRelation. It could >> still be worth removing it as a user-facing option to reduce confusion >> about memory tuning, but it wouldn't take out much code. What do you all >> think? >> >
