[
https://issues.apache.org/jira/browse/GEODE-9081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17311765#comment-17311765
]
ASF subversion and git services commented on GEODE-9081:
--------------------------------------------------------
Commit 7ac9d7e4f0d04c99298067ca0611d9326e96d9cf in geode's branch
refs/heads/develop from Jacob Barrett
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7ac9d7e ]
GEODE-9081: Remove transient allocation. (#6207)
* GEODE-9081: Remove transient allocation.
* New geode-unsafe access to non-SDK API for DirectBuffer.
* Use geode-unsafe to access DirectBuffer.attachment().
* Removes latency of reflection.
* Removes transient Object[] allocation in Method.invoke().
> Remove transient allocation when returning ByteBuffer to BufferPool.
> --------------------------------------------------------------------
>
> Key: GEODE-9081
> URL: https://issues.apache.org/jira/browse/GEODE-9081
> Project: Geode
> Issue Type: Improvement
> Components: core
> Reporter: Jacob Barrett
> Assignee: Jacob Barrett
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> {{BufferPool}} uses reflection to invoke a method when returning a
> {{ByteBuffer}}, which results in a transient {{Object[]}} variable argument
> allocation.
> The method being invoked is actually accessible through non-SDK APIs that are
> relatively stable. Add access to this method through {{geode-unsafe}} and
> avoid this allocation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
