We have a condition that affects all queries, lets say:
field: "CONDITION"
When we try to remove this field from all queries, DocumentDB CPU spikes and stays high, even after cache index / buffer hit ratio go back to almost 100%.
"field" is not part of any index, and it does not make any sense that removing it from query would destroy performances that much.
Any insights on what we are doing wrong ?
When rolling it back, it instantly goes back to normal, even if we roll back 4-5 hours later.