[SERVER-1675] expose gridFS calls to serverStatus() Created: 24/Aug/10  Updated: 06/Dec/22

Status: Open
Project: Core Server
Component/s: Performance
Affects Version/s: 1.6.1
Fix Version/s: features we're not sure of

Type: Improvement Priority: Major - P3
Reporter: Kenny Gorman Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query Execution
Participants:

 Description   

expose GridFS calls to serverStatus so we can see number of gridFS calls, as a bonus average size would be great.



 Comments   
Comment by Eliot Horowitz (Inactive) [ 25/Aug/10 ]

the database doesn't really know about grid fs per se.

You can even customize the collections used in the drivers.

So not sure how we could even do this generically.

Comment by Kenny Gorman [ 25/Aug/10 ]

hmm, so I guess what I want is a rollup of gridFS calls across all collections just like insert/query/update/delete... in serverStatus(). The idea being is one can see the difference between performance when gridFS is being used vs normal calls.

Comment by Eliot Horowitz (Inactive) [ 25/Aug/10 ]

GridFS is a spec, not a db feature per se, not sure it makes sense to track separately.

You can get per collection logging though

use admin

> db.runCommand( "top" ).totals["test.fs.files"]

> db.runCommand( "top" ).totals["test.fs.chunks"]

adding size to that makes sense though.
separate jira?

Comment by Kenny Gorman [ 24/Aug/10 ]

"opcounters" :

{ "insert" : 323355973, "query" : 310188302, "update" : 1847889, "delete" : 9, "getmore" : 0, "command" : 1855943, "gridFS" : 43 }

,

Generated at Thu Feb 08 02:57:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.