Commit 4a715a3
Add clarifying comments about paging behavior
Explain that system.local always has exactly 1 row and will never
require additional pages, while system.peers might need multiple
pages only for very large clusters (>1000 nodes). This addresses
the concern about serial page fetching - in practice, there's no
performance degradation because:
1. First pages are fetched in parallel via wait_for_responses
2. system.local never has additional pages (always 1 row)
3. system.peers rarely has additional pages (only for >1000 nodes)
4. Additional pages within a query must be serial (CQL protocol)
Co-authored-by: mykaul <4655593+mykaul@users.noreply.github.com>1 parent d7ac847 commit 4a715a3
1 file changed
Lines changed: 6 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
3660 | 3660 | | |
3661 | 3661 | | |
3662 | 3662 | | |
| 3663 | + | |
| 3664 | + | |
3663 | 3665 | | |
3664 | 3666 | | |
3665 | 3667 | | |
| |||
3841 | 3843 | | |
3842 | 3844 | | |
3843 | 3845 | | |
| 3846 | + | |
| 3847 | + | |
3844 | 3848 | | |
3845 | 3849 | | |
3846 | 3850 | | |
| |||
4148 | 4152 | | |
4149 | 4153 | | |
4150 | 4154 | | |
| 4155 | + | |
| 4156 | + | |
4151 | 4157 | | |
4152 | 4158 | | |
4153 | 4159 | | |
| |||
0 commit comments