gruuya commented on issue #7149: URL: https://github.com/apache/arrow-datafusion/issues/7149#issuecomment-1658441854
> Hm, it might not support mimalloc (according to readme it only supports jemalloc). Good point; to clarify I've been [profiling](https://github.com/splitgraph/seafowl/pull/424) and [optimizing](https://github.com/splitgraph/seafowl/pull/439) some stuff where we don't configure a custom allocator at all, so in the base case it appears to be working correctly. The peaks definitely seem to be real, as they lead to OOMs in memory-constrained envs. > Did you configure a memory limit? I haven't been setting a memory limit (neither in the above repro using datafusion-cli, nor in [seafowl itself](https://github.com/splitgraph/seafowl/blob/main/src/config/context.rs#L159-L162)). Naively it seems to me like top-k algorithm shouldn't be affected either way? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
