pmcgleenon commented on issue #16643: URL: https://github.com/apache/datafusion/issues/16643#issuecomment-3149617035
@Dandandan yes that's correct the previous runs were all using `c6a.4xlarge`. Recently the clickhouse team have added results for these additional instance types. It looks like this was done as part of a wider change to add them across multiple projects - [c6a.xlarge.json](https://github.com/ClickHouse/ClickBench/blob/main/datafusion-partitioned/results/c6a.xlarge.json) - [c6a.2xlarge.json](https://github.com/ClickHouse/ClickBench/blob/main/datafusion-partitioned/results/c6a.2xlarge.json) - [c8g.4xlarge.json](https://github.com/ClickHouse/ClickBench/blob/main/datafusion-partitioned/results/c8g.4xlarge.json) Also the datafusion tests are now separated into datafusion (single) and datafusion-partitioned (partitioned) directories https://github.com/ClickHouse/ClickBench/tree/main/datafusion-partitioned/results https://github.com/ClickHouse/ClickBench/tree/main/datafusion/results The published results for `c6a.xlarge` and `c6a.2xlarge` have `null` values in some of the tests which is a sign that OOM happened during the tests. So it seems like `c6a.4xlarge` is the minimum instance type to get valid results. I can think of a couple of options - either datafusion will not report results for `c6a.xlarge.json` and `c6a.2xlarge.json` or we figure out a way to run successfully on the lower memory systems. Maybe there's some configuration we can try. What do you think? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org
