|
| static constexpr uint32_t | kMaxValueSize = 2 * 1024 * 1024 |
| | Ceiling on max_value_size: the default connection low-water mark.
|
| |
| static constexpr uint32_t | kMaxSyncBatchBytes = 2 * 1024 * 1024 |
| | Ceiling on sync_batch_bytes, for the same reason.
|
| |
| static constexpr uint32_t | kMinSyncBatchBytes = 16 * 1024 |
| | Floor on sync_batch_bytes: below this a snapshot costs more in per-message framing and round trips than it saves in queue occupancy.
|
| |
Storage configuration.
The two size limits are not free parameters: both are bounded by what one peer's send queue can hold. A connection drops its peer as a slow consumer past its high-water mark (8 MiB by default, NodeConfig::send_queue_limit) and reports "no room" at a quarter of it, so a single value — and a single snapshot chunk — must stay well inside that quarter, or the very first one would kill the link it travels on. Both are clamped to kMaxValueSize / kMaxSyncBatchBytes on construction and in set_config().
Definition at line 188 of file storage.h.