Note
This parameter is available starting with V4.6.3.
Overview
dtl_compress_func specifies the compression algorithm used for DTL (Data Transfer Layer) cross-node RPC messages during SQL parallel execution. The default is lz4_1.0. Setting it to none disables compression. This configuration's algorithm selection does not take effect when the hidden parameter _px_message_compression is set to false.
After the compression algorithm is configured, the modification takes effect on newly initialized DFCs (Data Transmission Flow Control contexts), but does not change the compression algorithms of existing DFCs or their channels.
Privilege requirements
Query parameters
Both the
systenant and all user tenants can query this parameter using theSHOW PARAMETERSstatement or theGV$OB_PARAMETERSview.Modify parameters
Both the
systenant and user tenants can use theALTER SYSTEM SETstatement to modify this parameter.
Attributes
Attribute |
Description |
|---|---|
| Parameter type | String |
| Default Value | lz4_1.0 |
| Value range |
|
| Modifiable | Yes, you can use theALTER SYSTEM SETStatement modification. |
| Whether to restart the OBServer node for the change to take effect | No, the setting takes effect immediately. |
Usage instructions
Value description
Value |
Meaning |
|---|---|
none |
Compression is not performed and the data is sent as the original payload. |
lz4_1.0 |
Uses the existing LZ4 implementation, which is the default algorithm. |
snappy_1.0 |
Implement using the existing Snappy. |
zstd_1.3.8 |
The existing ZSTD 1.3.8 implementation is used, with the compression level fixed at level 1. |
zstd_1.5.7 |
The existing ZSTD 1.5.7 implementation is used, with the compression level fixed at level 1. |
Effective rules
Each time DFC is initialized, the system reads the tenant's
_px_message_compressionanddtl_compress_functo determine the valid compression algorithm and passes it to the corresponding channel and broadcast service.When
_px_message_compressionis set tofalse, the subsequently initialized DFC does not enable compression and is not affected by the algorithm selected bydtl_compress_func.When
_px_message_compressionistrue, thedtl_compress_funcselection algorithm is used; wherenonestill indicates no compression.The algorithm is fixed during DFC initialization and is not re-read for each packet transmission. Dynamic modification does not switch the algorithm of existing DFCs or their channels.
The effective boundary is the DFC, not the entire SQL statement. Different nodes or different initialization times may use different algorithms for the DFC, so query-level atomic switching is not guaranteed.
Only the values listed in the allowlist above are accepted; invalid names will be rejected. Streaming compression, hardware-specific compression, and other algorithms intended solely for the storage layer are not supported.
Message processing and compatibility
Normal sending, batch/aggregated sending, and broadcasting all pass the effective algorithm to the RPC layer; local channels do not introduce a new network compression process.
The message header retains the existing compression algorithm ID and original length fields. The receiver selects the decompression algorithm based on the message header, without relying on the receiver's current tenant configuration.
No new compression algorithm IDs are added, nor is the DTL serialization layout or RPC protocol format modified.
If the volume does not decrease after compression, the existing RPC logic is retained and the original payload is sent back.
Usage recommendations
For general scenarios, it is recommended to keep the default value
lz4_1.0.For tenants with limited bandwidth but sufficient CPU resources, you can test ZSTD and decide whether to switch based on network load, CPU utilization, and actual SQL execution time.
Snappy and different versions of ZSTD are provided as optional solutions. Their performance is not guaranteed to be superior to the default LZ4 for all data and workloads.
To disable subsequent DTL compression, you can set this parameter to
noneor set_px_message_compressiontofalse. Neither of these will modify the already initialized DFC.If the main switch is already off, changing only
dtl_compress_functo another algorithm will not re-enable compression. You must also set_px_message_compressiontotrue.In the synthetic sample encoding/decoding test for 64 KiB chunks, ZSTD 1.5.7 achieved approximately 30% lower load and 38% lower load compared to LZ4 in TPC-H and TPC-DS scenarios, respectively. However, its encoding/decoding throughput was lower. This result does not represent a performance improvement for complete SQL queries.
Scope of application
This parameter only controls the compression of DTL cross-node RPC messages during SQL parallel execution. It does not control client connection compression, table storage compression, shared storage access, or log transmission compression. It also does not provide SQL-level hints, session-level configuration, compression level adjustment, or runtime adaptive algorithm selection.
Configuration example
The following example is executed in the target user tenant. The modification affects newly initialized DFCs after configuration propagation, without switching existing channels.
-- Enable the general compression switch and use the default LZ4 algorithm.
ALTER SYSTEM SET _px_message_compression = true;
ALTER SYSTEM SET dtl_compress_func = 'lz4_1.0';
-- Use Snappy
ALTER SYSTEM SET dtl_compress_func = 'snappy_1.0';
-- Using ZSTD 1.5.7
ALTER SYSTEM SET dtl_compress_func = 'zstd_1.5.7';
-- Disable Subsequent DTL Compression by Using the Algorithm Option
ALTER SYSTEM SET dtl_compress_func = 'none';
-- or turned off by the existing master switch; in this case, the algorithm selection does not take effect.
ALTER SYSTEM SET _px_message_compression = false;
-- Restore default compression behavior: Restore both the general switch and the default algorithm.
ALTER SYSTEM SET _px_message_compression = true;
ALTER SYSTEM SET dtl_compress_func = 'lz4_1.0';
-- View the configuration. The configured value may not be the valid algorithm of the existing channel.
SHOW PARAMETERS LIKE 'dtl_compress_func';