fio VS QuestDB

Assuming two systems use flash storage, network bandwidth is identical and it is configured the same way, there should be an issue within the PC, either system or storage drive. Check the system logs for errors and warning events related to data transfer from/to NAS. Try to benchmark the PCs' disks using fio to confirm they have similar performance. https://github.com/axboe/fio

Not specifically addressing your question, but when you get to the point of wanting to start doing some experiments you may find that 'fio' [1] is very handy.

[1] https://github.com/axboe/fio

The dd is not a good benchmarking tool, you should use something like fio and probably tune it to use the ioengine most similar to your use case (eg. a database server will probably use some async IO interface). In your first example (with bs=1G) probably something (the guest OS, the qemu/kvm or the host OS) have split into smaller chunks anyway.

All linux tests are run with fio 3.32 (github) with future commit 03900b0bf8af625bb43b10f0627b3c5947c3ff79 manually applied.

FIO: https://github.com/axboe/fio

Agree, I used flex/yacc to add an arithmetic expression evaluator to fio a few years back to allow simple math with some units in fio's job files, and for stuff like that, they're fine, but I wouldn't want to use them for a real language, the error handling is kind of a nightmare.

Flexible I/O Tester (fio-3.33): https://github.com/axboe/fio

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!