taichi VS QuestDB

taichi – Productive, portable, and performant GPU programming in Python

ETH Zurich is using it for their physics sim courses, University of Utah is using it for simulations (SIGGRAPH 2022), OPPO (they make smart devices running Android), Kuaishou uses it for liquid and gas simulation on GPUs. Lots of GPU accelerated sim stuff.

https://www.taichi-lang.org/

https://www.researchgate.net/publication/337118128_Taichi_a_...

https://github.com/taichi-dev/taichi

Check our the realease note (https://github.com/taichi-dev/taichi/releases) for more improvements.

I've recently started using Taichi (https://taichi-lang.org/) for numerical codes and the fact it doesn't try to trick you into thinking it's numpy is a nice "feature". ;)

Taichi v1.4.0 is released! See what's new: - Taichi AOT, along with a native Taichi Runtime library: Native applications can now load compiled AOT modules and launch Taichi kernels without a Python interpreter. - Taichi ndarray: An array object that holds contiguous multi-dimensional data to allow easy data exchange with external libraries. - Dynamic index: Use variable indices whenever necessary on all backends without affecting the performance of those matrices with only constant indices. See deprecation and more improvements in the release note.

Oh, then if you're not already tied to any particular VFX software, I might as well recommend Taichi again.

It's an upgrade of a basic version. See changes to the source code here: https://github.com/taichi-dev/taichi/pull/6851

If your data lacks uniform time intervals between consecutive entries, QuestDB offers a solution by allowing you to sample your data. After that, MindsDB facilitates creating, training, and deploying your time-series models.

If you're interested in that functionality or have any other feedback, please drop by our open source repository or community Slack and let us know.

QuestDB is a high-performance time series database with SQL analytics that can power through market data ingestion and analysis. It's open source and integrates well with the tools and languages you use. Check us out!

Looks like full keys are always compared if hash codes test equal, which is what I'd expect. For example: https://github.com/questdb/questdb/blob/master/core/src/main...

But of course, I want to run a QuestDB instance on my node, which uses two additional TCP ports for Influx Line Protocol (ILP) and Pgwire communication with the database. So how can I expose these extra ports on my node and route traffic to the QuestDB container running inside of k3s?

In this post, I will detail a way in which I recently used annotations while writing an operator for my company's product, QuestDB. Hopefully this will give you an idea of how you can incorporate annotations into your own operators to harness their full potential.

QuestDB is an open source, high performance time series database. With its massive ingestion throughput speeds and cost effective operation, QuestDB reduces infrastructure costs and helps you overcome tricky ingestion bottlenecks. Thanks for reading!