You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The raw flag might let us skip BSON parsing, but let's check the source to be sure. We can't use that data efficiently, but it'll help us better understand the "mongo time" piece of the puzzle.
The showDiskLoc flag might show us if we're doing a bunch of random reads for each request. On the mongolab shared plan, I'm pretty sure we're effectively using a magnetic hard drive underneath, as opposed to SSD.
The exhaust flag might avoid some round trips to issue the getMore requests.
If I get a chance to test these, I'll let you know.
The text was updated successfully, but these errors were encountered:
Via @prashtx:
I was poking around for a way to get skip BSON parsing in the node mongodb driver. I found some interesting things on this page that could pertain to nodetiles/our performance investigations.
http://mongodb.github.io/node-mongodb-native/api-generated/cursor.html
In particular:
The raw flag might let us skip BSON parsing, but let's check the source to be sure. We can't use that data efficiently, but it'll help us better understand the "mongo time" piece of the puzzle.
The showDiskLoc flag might show us if we're doing a bunch of random reads for each request. On the mongolab shared plan, I'm pretty sure we're effectively using a magnetic hard drive underneath, as opposed to SSD.
The exhaust flag might avoid some round trips to issue the getMore requests.
If I get a chance to test these, I'll let you know.
The text was updated successfully, but these errors were encountered: