MongoBooster Support website buggy
Solved
I've reported a problem yesterday.
You answered and provided me a link in the email to answer your questions.
But the link doesnt work, I get a 500 error.
Also, when accessing my history of ticket, it seems that they are not clickable...
To answer your questions about `Disable mockup script ` :
I run with mongo 3.2.1.
db.omnipage.stats() gets me
- {
- "avgObjSize" : 93683,
- "capped" : false,
- "count" : 820,
- "indexSizes" : {
- "_id_" : 57232,
- "scanId_1" : 106288
- },
- "lastExtentSize" : 46333952,
- "nindexes" : 2,
- "ns" : "foo.bar",
- "numExtents" : 8,
- "ok" : 1,
- "paddingFactor" : 1,
- "paddingFactorNote" : "paddingFactor is unused and unmaintained in 3.0. It remains hard coded to 1.0 for compatibility only.",
- "primary" : "set-56bb1207f25355000e0005ee",
- "sharded" : false,
- "size" : 76820160,
- "storageSize" : 115888128,
- "totalIndexSize" : 163520,
- "userFlags" : 1
- }
Those objects are quite big.
db.omnipage.getIndexes() is executed in ~0.110 secs.
db.omnipage.find({}).sort({_id:-1}).limit(5) is executed in ~0.677 secs.
Thank you
It looks a little strange. The fields info fetch time equals to "getIndexes()+find({}).limit(5)", it should be about 0.8 secs.
I want to know how fast the connection is.
It looks a little strange. The fields info fetch time equals to "getIndexes()+find({}).limit(5)", it should be about 0.8 secs.
I want to know how fast the connection is.
The speed depends, really. Sometimes fast, sometimes slow.
Anyway, my suggestion was to simply provide an options to disable the automatic execution.
Most of the times when I open a collection, I will edit the query anyway, so I see no need to pre-execute the `find({})`, unless it's instant (which is not) and doesnt block my workflow (which it does).
Thank you
The speed depends, really. Sometimes fast, sometimes slow.
Anyway, my suggestion was to simply provide an options to disable the automatic execution.
Most of the times when I open a collection, I will edit the query anyway, so I see no need to pre-execute the `find({})`, unless it's instant (which is not) and doesnt block my workflow (which it does).
Thank you
If you just want to disable automatic execution, just hold "shift" key when you open collection.
If you just want to disable automatic execution, just hold "shift" key when you open collection.
Sweet! That's nice.
Is it possible to have it as a deactivable option in the future?
Sweet! That's nice.
Is it possible to have it as a deactivable option in the future?
OK, I will consider it.
OK, I will consider it.
Thank you Qinghai
Thank you Qinghai
Replies have been locked on this page!