Lorenzo Mangani

@danthegoodman1 this was just a blocker being removed, still quite a bit of of [work](https://github.com/chdb-io/chdb/pull/81) to be done before its usable, stay tuned!

Hey @simonw thanks for the suggestion! If the method you mentioned works, feel free to raise a PR and we'll try it out! I'm not an expert but my understanding...

Thanks for the report @l1t1 we appreciate it! This definitely helps refine our scope. The next chdb versions should improve any gaps in performance, although clickhouse-local and chdb are built...

Thanks for the @l1t1 this is interesting and most likely means the performance issue is related to jemalloc use in chdb or even with build options for certain processors or...

@alexey-milovidov any input or comments on this intent and related opportunities from the ClickHouse team?

@zhanglistar true, but we already strip libchdb.so which brings it to about ~380MB uncompressed and ~100MB compressed.

> One downside: if it is not tested by ClickHouse CI, it will most likely contain a ton of bugs, and having these bugs will lead to reputational risks for...

The current support is barely plaintext only. To properly support POST data (including binary formats) we should expose a data hook in chdb equivalent to stdin (or --data) in clickhouse-local...

The data pipe won't be available until future versions of chdb will support it without stdin hacks. I've implemented a workaround in 0.15.3 which should work around the newline issues...

The workaround was weak and didn't cover binary protocols. so as predicted this needs an stdin hack to function. Here's a prototype to test: https://github.com/chdb-io/chdb-server/pull/11