three/four potential seg faults for non in mem yielding
disk/yield lock - initial query
disk/yield lock - any update
improve not in mem yielding hash function
for non in mem yielding, touch / check whole record not just beginning
not in mem yielding for single doc delete
not in mem yield processGetMore
make sure yieldSometimes RecordNeeds specs are appropriate
Q1. Do you mean the memory-mapped file disk I/O operations?
Q2. Do you mean writing operations and write-lock?
wow, fixed, cool, thanks!
mongo-10gen-unstable still refers to 1.9.0 when do you plan to switch it to 1.9.1?
Will 2.0 contains this fix?
Note fix for and status above.
Was put in 1.9.1 - so yes.
Is this first phase visible in performance metrics? We're not noticing any difference during load tests.
@remon are you doing one of these, and physical disk io is high?
> update by _id
> long cursor iteration