[
https://issues.apache.org/jira/browse/ASTERIXDB-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17944628#comment-17944628
]
ASF subversion and git services commented on ASTERIXDB-3587:
------------------------------------------------------------
Commit c21f99f3359c3ac52eb0080ef7bdab94daf31a8f in asterixdb's branch
refs/heads/master from Ali Alsuliman
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=c21f99f335 ]
[ASTERIXDB-3587][RT] Re-use frame in NL join cache activity
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
Instead of creating a frame for each incoming frame, create
one frame and re-use it in the cache activity of the nested
loop join operator.
- Reduce the logging level for some logs from debug to trace.
Ext-ref: MB-66027
Change-Id: I267d227f6a5e435e08221cb94895cedf60764e4c
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/19561
Integration-Tests: Jenkins <[email protected]>
Tested-by: Ali Alsuliman <[email protected]>
Reviewed-by: Ali Alsuliman <[email protected]>
Reviewed-by: Murtadha Hubail <[email protected]>
> Nested loop join allocates bytebuffer per frame
> -----------------------------------------------
>
> Key: ASTERIXDB-3587
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-3587
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: RT - Runtime
> Reporter: Ali Alsuliman
> Assignee: Ali Alsuliman
> Priority: Major
> Labels: triaged
>
> The cache activity of the nested loop join operator allocates a byte buffer
> for each incoming frame. One frame could be allocated and re-used when the
> incoming frames do not change in size which is typically the case.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
