Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6227#issuecomment-103210115
@rxin @zsxwing In the long term, I think that we should consider a more
complete design for buffer pooling in our allocator, including thinking through
how / whether we want to support pooling for off-heap modes, how we want to
match up allocation requests with things in the pages, whether we want to have
more manual control over purging pages from the pool, etc. For the immediate
1.4 term, though, I think a super-simple approach like the one in this patch
offers a nice improvement. Because the number of different allocation sizes is
relatively small (one or two sizes, tops), I think the simple approach is fine
for starters.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
