Timeline for Azure Cosmos: MongoDB sharded cluster: $in query performance degrades with fewer values
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 23 at 22:11 | comment | added | Joe | What does the document load time look likefor those? | |
| Oct 23 at 11:54 | history | edited | Markus | CC BY-SA 4.0 |
Formatted query plan
|
| Oct 23 at 4:12 | comment | added | 9308 | @Joe Yes, but for larger range queries using the same query structure and same index - which might scan 6 times more documents (over 865k docs) - the results are returned in milliseconds. | |
| Oct 23 at 2:25 | comment | added | Joe | That explain indicates 34s out of 43s runtime was spent loading docs. Seems slow for 865k docs totalling 400MB | |
| Oct 23 at 1:47 | comment | added | 9308 | @YongShun, yes, i have already tried that but no luck. | |
| Oct 23 at 1:45 | comment | added | Yong Shun |
AFAIK, try to avoid using hint as the MongoDB query optimiser will choose the best index for querying performance. Unless you confirmed that your sessionId_1_timestamp_-1 index is the best index to perform such query. blog.thnkandgrow.com/…
|
|
| Oct 23 at 1:45 | comment | added | 9308 | @FranckPachot, sure, i have updated it in the problem statement. Please see. | |
| Oct 23 at 1:44 | history | edited | 9308 | CC BY-SA 4.0 |
added 2326 characters in body
|
| Oct 22 at 18:36 | comment | added | FranckPachot | can you show the execution plan: .explain("executionStats") | |
| Oct 22 at 15:28 | history | edited | aneroid | CC BY-SA 4.0 |
improved formatting
|
| S Oct 22 at 15:21 | review | First questions | |||
| Oct 22 at 16:17 | |||||
| S Oct 22 at 15:21 | history | asked | 9308 | CC BY-SA 4.0 |