Details
-
Bug
-
Resolution: Won't Fix
-
Major - P3
-
None
-
mongo 3.0+ mongo-c-driver(master)
*Location*: http://docs.mongodb.org/manual/reference/method/cursor.batchSize/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.85 Safari/537.36
*Referrer*: https://www.google.com.hk/
*Screen Resolution*: 1680 x 1050
*repo*: docs
*source*: reference/method/cursor.batchSize
mongo 3.0+ mongo-c-driver(master) *Location*: http://docs.mongodb.org/manual/reference/method/cursor.batchSize/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.85 Safari/537.36 *Referrer*: https://www.google.com.hk/ *Screen Resolution*: 1680 x 1050 *repo*: docs *source*: reference/method/cursor.batchSize
-
0.25
Description
Usually people want to know why some driver will come up with this concept.And how to make a good strategy to achieve better performance.