[
https://issues.apache.org/jira/browse/ASTERIXDB-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15727089#comment-15727089
]
ASF subversion and git services commented on ASTERIXDB-1746:
------------------------------------------------------------
Commit 1170755c9d97f6552b2f2fee73687d0be1ee8670 in asterixdb's branch
refs/heads/master from [~wangsaeu]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=1170755 ]
ASTERIXDB-1746: no excessive new byte[] allocation during a record build
- During a record write using RecordBuilder.write(), it allocates two new
byte[]
using toByteArray() method. We can replace it to getByteArray() method and
this reduces a lot of new byte[] allocation.
Change-Id: Ibdbc6314abd72d2a93978da49ea406c3c38731d2
Reviewed-on: https://asterix-gerrit.ics.uci.edu/1376
Sonar-Qube: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Reviewed-by: Ian Maxon <[email protected]>
> Excessive new byte[] array constructions during record writes using
> RecordBuilder.write()
> -----------------------------------------------------------------------------------------
>
> Key: ASTERIXDB-1746
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1746
> Project: Apache AsterixDB
> Issue Type: Bug
> Reporter: Taewoo Kim
> Assignee: Taewoo Kim
>
> During a record write using RecordBuilder.write(), it allocates two new
> byte[] using toByteArray() method. The consequence of this is allocating a
> lot of new byte[] array, thus may lead an excessive garbage collection. It
> can be replaced as getByteArray() method. The fix will be soon uploaded.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)