Skip to content

Commit c7e078e

Browse files
Incorporate feedback on resharding performance section
- Refine content based on review feedback - Improve clarity and technical accuracy of resharding documentation - Update performance characteristics and factor descriptions - Enhance readability and flow of the resharding process explanation
1 parent ced63b8 commit c7e078e

File tree

1 file changed

+5
-13
lines changed

1 file changed

+5
-13
lines changed

content/operate/rs/databases/memory-performance/memory-limit.md

Lines changed: 5 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ If you observe this behavior, consider [monitoring]({{< relref "/operate/rs/moni
8383

8484
Resharding enables you to increase database capacity by adding shards and utilizing more cluster memory. Understanding resharding duration helps you plan maintenance operations and minimize database risk.
8585

86-
### Resharding process overview
86+
### Resharding overview
8787

8888
Resharding follows a three-stage process for each new shard:
8989

@@ -99,26 +99,18 @@ Resharding is an atomic operation that cannot be interrupted. Database corruptio
9999

100100
Flexible sharding optimizes the key trimming stage, significantly reducing the time required to remove unnecessary keys from original shards.
101101

102-
### Duration characteristics
102+
### Resharding duration factors
103103

104-
Resharding duration increases linearly with the number of keys in your database. Several factors affect resharding duration:
104+
Resharding duration increases linearly with the number of keys in your database. Flexible sharding, key length, and network traffic affect resharding duration:
105105

106-
### Flex sharding impact
106+
Flexible sharding improves resharding duration compared to standard sharding.
107107

108-
Flex sharding improves resharding duration compared to standard sharding.
109-
110-
### Key length considerations
111-
112-
Key length directly affects resharding duration. Longer keys require more time to process due to increased hash calculation overhead per key.
113-
114-
The decrease in duration provided by flex sharding varies based on key length:
108+
Key length directly affects resharding duration. Longer keys require more time to process due to increased hash calculation overhead per key. The decrease in duration provided by flex sharding varies based on key length:
115109

116110
- **Short keys (10 bytes)**: Flex sharding provides up to 50% improvement
117111
- **Long keys (2000 KB)**: Flex sharding provides minimal improvement (approximately 11%)
118112
- **Critical threshold**: Between 50-100 bytes, flex sharding advantages begin to diminish
119113

120-
### Traffic impact during resharding
121-
122114
Network traffic has a measurable but limited effect on resharding duration. Since resharding operations typically don't reach CPU limits, the impact on both resharding time and ongoing traffic remains minimal.
123115

124116
## Memory metrics

0 commit comments

Comments
 (0)