[DOCS-4842] Add note on cursor batchSize about performance for long running queries Created: 17/Feb/15 Updated: 30/Oct/23 Resolved: 01/Nov/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Roger McCoy (Inactive) | Assignee: | Ravind Kumar (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 1 year, 14 weeks, 1 day ago | ||||
| Epic Link: | DOCSP-1769 | ||||
| Description |
|
In the document on Cursor Batches, it might be mentioned that setting a non-zero batchSize can be used to reduce the time needed for a cursor to do a getmore operation. More details on sharded environment - there can be wide variation in performance times between the intiial query, the first getmore operation, and then subsequent getmore operations. Using a non-zero batchSize will reduce the variation in performance times. |
| Comments |
| Comment by Education Bot [ 01/Nov/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |