[
https://issues.apache.org/jira/browse/IGNITE-24756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Korotkov updated IGNITE-24756:
-------------------------------------
Description:
{color:#ff0000}WIP{color}
Works for s = 0.01 but do not complete in 5 minutes for s=0.1 and s=1.0
Use a lot of heap on client side (look similar to the #16 case at IGNITE-24753)
***
Load test (1 client node, 3 server nodes) shows that there is huge HEAP memory
usage on the client side.
For scale=0.01 it were executed about 700 queries in 5 seconds. With average
2.99Mb and 5.68Mb of heap allocation per request (on client and server
correspondingly).
For scales 0.1 and 1.0 single query was calcelled after 5 minutes, having
Gigabytes of allocated per the single query.
was:
{color:#ff0000}WIP{color}
Works for s = 0.01 but do not complete in 5 minutes for s=0.1 and s=1.0
Use a lot of heap on client side (look similar to the #16 case at IGNITE-24753)
> Calcite. TPC-H query #19: too long execTime and high heap memory usage on
> client
> --------------------------------------------------------------------------------
>
> Key: IGNITE-24756
> URL: https://issues.apache.org/jira/browse/IGNITE-24756
> Project: Ignite
> Issue Type: Bug
> Reporter: Sergey Korotkov
> Assignee: Ilya Shishkov
> Priority: Major
> Labels: ise, tpch
>
> {color:#ff0000}WIP{color}
> Works for s = 0.01 but do not complete in 5 minutes for s=0.1 and s=1.0
> Use a lot of heap on client side (look similar to the #16 case at
> IGNITE-24753)
> ***
> Load test (1 client node, 3 server nodes) shows that there is huge HEAP
> memory usage on the client side.
> For scale=0.01 it were executed about 700 queries in 5 seconds. With average
> 2.99Mb and 5.68Mb of heap allocation per request (on client and server
> correspondingly).
> For scales 0.1 and 1.0 single query was calcelled after 5 minutes, having
> Gigabytes of allocated per the single query.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
