This is one of the most useful web tools I've ever seen.
I work on connectors for datasources (mostly DB's. Being able to quickly test things like sorting behavior and how the same function can be emulated across DB's would have made my life so much easier.
> We can PoC the Firecracker VM Escape on that service.
Does this mean you ran the exploit on your service and confirmed it worked? If so, why would you be advertising this, lol. Unless you've already patched?
We are building our compiler and the entire LLVM toolchain with PGO, and it gives a solid 20..30% improvement in build speed*. At the same time, building ClickHouse with PGO does not give any meaningful improvement.
ClickHouse has been tested with jemalloc, mimalloc, tcmalloc (both variants), rpmalloc, lfalloc, hualloc, and ended up using jemalloc after a few patches and bug fixes.
I keep a personal list of links to defend my non-AI stance. It is weird I even need to. If I am a carpenter and I was ordered to use a robot and tell it what to do there would be lawsuits and what not but as a software developer I am the idiot that does not want to modernize.
I've also built a visualizer into ClickHouse, so we can analyze its binary: https://play.clickhouse.com/binary?user=binary - which code takes more space, what dependencies are too big, or what template instantiations are bloated.
It hosts hundreds of database engines - many of them have vulnerabilities, and some of them, like Pandas, are basically open RCEs regardless.
We can PoC the Firecracker VM Escape on that service.
reply