pdeng
September 25, 2025, 1:05pm
1
Hi there,
InfluxDB supports gzip message to optimise ILP ingestion.
Can QuestDB support it? I cannot find anywhere to configure it, or do you have ETA for this feature?
Cheers,
Paul
Should come in next release:
master ← nw_ilp_gzip
opened 11:16PM - 19 Sep 25 UTC
ILP can be fairly inefficient with bandwidth. A 2x-3x increase in bandwidth woul… d not be unusual for ILP streaming, due to its text protocol nature.
Upgrading the clients to a binary protocol is a WIP. In the meantime, this change allows the server to accept `gzip` encoded ILP.
In a local test, this will reduce overall throughput, due to the overhead of encoding and decoding the compressed buffer:
**TSBS, cpu-only**
- Uncompressed, 1 thread: `568582 rows/sec`
- Compressed, 1 thread: `295322 rows/sec`
- Uncompressed, 8 threads: `1333824 rows/sec`
- Compressed, 8 threads: `785233 rows/sec`
However, in aggregate, this can be an advantage; for example, when receiving text-heavy data from multiple sources (logs, documents). The encoding cpu-overhead is masked on the client-side, and the reduction in bandwidth usage raises the ceiling for maximum throughput.
Nom
April 28, 2026, 12:07pm
3
ILP gave me a few headaches, I was able to ingest roughly 22k rows a second using the basic batching and Bun js. Dynamically flushing when it hit the params (total column) limit and query size limit.
We’re imminently releasing a new wire protocol which deprecates ILP. It is faster, and much more efficient. Look out in the next couple of weeks
pdeng
May 27, 2026, 9:24am
5
Any eta for the release?
Code is already merged on the main repository, but we are still finishing work in some of the clients. We should be releasing pretty soon.
