[
https://issues.apache.org/jira/browse/HAWQ-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Goden Yao updated HAWQ-974:
---------------------------
Description:
As for now PXF Bridge api returns whole fragment, which might be big amount of
data sometimes. So instead, it should be able to stream fixed size pages.
Criteria of choosing page size - GC activity should be in some reasonable range
0-5%.
*workaround*
right now, user can increase the heap size allocated to PXF to mitigate the
issue but it's not recommended as pxf java process should not need that much
heap size for every node, which puts memory in low efficiency for other
applications.
was:
As for now PXF Bridge api returns whole fragment, which might be big amount of
data sometimes. So instead it should be able to stream fixed size pages.
Criteria of choosing page size - GC activity should be in some reasonable range
0-5%.
> PXF Bridge api should stream data as pages
> ------------------------------------------
>
> Key: HAWQ-974
> URL: https://issues.apache.org/jira/browse/HAWQ-974
> Project: Apache HAWQ
> Issue Type: Improvement
> Components: PXF
> Reporter: Oleksandr Diachenko
> Assignee: Goden Yao
> Fix For: backlog
>
>
> As for now PXF Bridge api returns whole fragment, which might be big amount
> of data sometimes. So instead, it should be able to stream fixed size pages.
> Criteria of choosing page size - GC activity should be in some reasonable
> range 0-5%.
> *workaround*
> right now, user can increase the heap size allocated to PXF to mitigate the
> issue but it's not recommended as pxf java process should not need that much
> heap size for every node, which puts memory in low efficiency for other
> applications.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
