yuanbiao
/
emqx
1
0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs(ds): Apply remarks

This commit is contained in:
ieQu1 2024-02-23 13:41:05 +01:00
parent c18fc6a4bb
commit dd2e35345f
No known key found for this signature in database
GPG Key ID: 488654DF3FED6FDE
1 changed files with 21 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
rel/i18n/emqx_ds_schema.hocon
View File

@ -13,7 +13,9 @@ builtin.desc:
builtin_data_dir.label: "Database location" builtin_data_dir.label: "Database location"
builtin_data_dir.desc: builtin_data_dir.desc:
"""~ """~
File system directory where the database is located.~""" File system directory where the database is located.
By default it is equal to `node.data_dir`.~"""
builtin_n_shards.label: "Number of shards" builtin_n_shards.label: "Number of shards"
builtin_n_shards.desc: builtin_n_shards.desc:
@ -33,19 +35,32 @@ builtin_layout.desc:
"""~ """~
Storage layout is a method of arranging messages from various topics and clients on disc. Storage layout is a method of arranging messages from various topics and clients on disc.
Depending on the type of workload and the topic structure, different types of strategies for storing the data can be employed to maximize efficency of the replay.~""" Depending on the type of workload and the topic structure, different types of strategies for storing the data can be employed to maximize efficiency of reading messages from the durable storage.~"""
layout_wildcard_optimized.label: "Wildcard-optimized storage layout" layout_wildcard_optimized.label: "Wildcard-optimized storage layout"
layout_wildcard_optimized.desc: layout_wildcard_optimized.desc:
"""~ """~
_Wildcard-optimized_ layout is designed to maximize the throughput of the wildcard subscriptions covering large numbers of topics.~""" _Wildcard-optimized_ layout is designed to maximize the throughput of wildcard subscriptions covering large numbers of topics.
wildcard_optimized_epoch_bits.label: "Epoch size" For example, it can handle scenarios where a very large number of clients publish data to the topics containing their client ID, such as: `sensor/%device-version%/%clientid%/temperature`, `sensor/%device-version%/%clientid%/pressure`, etc.
This layout will automatically group such topics into a single stream, so a client subscribing to a topic filter containing wildcards (such as `sensor/+/+/temperature`) will be able to consume messages published by all devices as a single batch.
This layout is efficient for non-wildcard subscriptions as well.~"""
wildcard_optimized_epoch_bits.label: "Epoch bits"
wildcard_optimized_epoch_bits.desc: wildcard_optimized_epoch_bits.desc:
"""~ """~
Wildcard-optimized layout partitions messages recorded at different times into "epochs". Wildcard-optimized layout partitions messages recorded at different times into "epochs".
Each epoch can be consumed by the subscribers as a batch. Reading messages from a single epoch can be done very efficiently, so larger epochs improve the throughput of subscribers, but may increase end-to-end latency
Generally, larger epochs lead to higher throughput of subscribers, however currently they may increase latency.~"""
Time span covered by each epoch grows exponentially with the value of `epoch_bits`:
- `epoch_bits = 1`: epoch time = 1 millisecond
- `epoch_bits = 2`: 2 milliseconds
...
- `epoch_bits = 10`: 1024 milliseconds
- `epoch_bits = 13`: ~8 seconds
....~"""
egress_max_items.label: "Max items" egress_max_items.label: "Max items"
egress_max_items.desc: egress_max_items.desc: