Compatibility, tracked.
Generated from the PeachQ conformance ledger: q behaviour coverage, trend, suite heatmap, and robustness checks from the current build.
Roadmap: what doesn't work yet
PeachQ 0.92 reads and writes kdb+ on-disk data, including partitioned and segmented databases. The main gaps now are:
- Performance. Queries on a partitioned database give correct results but are not yet efficient. Each query builds one in-memory table from the partitions it reads, so a large historical database (HDB) will be much slower than kdb+ and use far more memory.
- Multi-threading. Query execution does not yet spread work across cores as kdb+ does.
- Snappy-compressed and encrypted files do not read yet. gzip and lz4 do.
If your firm runs kdb+ in production, talk to us. We have spent a lot of time ironing out the edge cases of running real q applications such as TorQ, and real workloads decide what we build next. Talk to us
| Project | Author | About | Stars | Grade | Tests |
|---|
When we rerun the list, any project whose results drop is flagged, so we see changes in PeachQ that would break it. Authors are also thanked on the thanks page. To show your project's grade in its README, use [](https://peachq.org/compatibility#app-NAME).