Closed dandv closed 10 years ago
Hmm.
Good idea.
Arunoda Susiripala I curate Meteor Weekly - Check it out!http://meteorhacks.com/meteor-weekly/?utm_source=email-footer&utm_medium=email&utm_campaign=meteorweekly
On Mon, May 19, 2014 at 8:38 PM, Dan Dascalescu notifications@github.comwrote:
The guides on reducing network impact and response time are great.
A guide on "not using oplog", maybe even hyperlinked from the trace, would be good too.
[image: image]https://cloud.githubusercontent.com/assets/33569/3015863/5ce70594-df67-11e3-83d8-d6ebf0d40c84.png
— Reply to this email directly or view it on GitHubhttps://github.com/arunoda/meteor-apm-client/issues/43 .
https://github.com/meteor/meteor/wiki/Oplog-Observe-Driver would be a good start.
A guide would be useful indeed. I've read that meteor wiki post but don't see what applies to my query:
collection : content
selector: {"pubDate":{"$gt":"1900-02-01T08:00:00.000Z"},"$or":[{"ct":"article"},{"score":{"$gt":10}}]}
function : observeChanges
isCursorMethod: true
fields: {"body":0}
sort: {"pubDate":-1,"title":1}
limit: 100
oplog: false
noOfHandles: 1
noOfCachedDocs: 100
Actually, now Meteor can handle most of the queries (including this one). Although, let's see if we can work some per query based guide.
Arunoda Susiripala
@arunoda http://twitter.com/arunoda http://gplus.to/arunodahttps://github.com/arunoda http://www.linkedin.com/in/arunoda
On Mon, May 19, 2014 at 8:49 PM, Dan Dascalescu notifications@github.comwrote:
A guide would be useful indeed. I've read that meteor wiki post but don't see what applies to my query:
collection : content selector: {"$or":[{"cik":{"$in":["0001318605","0000037996",..."]}},{"companyId":{"$in":["G6j7T37botemkQPYd",...]}},{"companies.stockbase.matched._id":{"$in":["G6j7T37botemkQPYd",...]}}]} function : observeChanges isCursorMethod: true fields: {"body":0} sort: {"pubDate":-1,"cik":1} limit: 100 oplog: false noOfHandles: 1 noOfCachedDocs: 100
— Reply to this email directly or view it on GitHubhttps://github.com/arunoda/meteor-apm-client/issues/43#issuecomment-43517531 .
Ah, nevermind, I was running the app in production, not with meteor run
, and didn't have the replica set and oplogger user set up.
Okay.
Arunoda Susiripala
@arunoda http://twitter.com/arunoda http://gplus.to/arunodahttps://github.com/arunoda http://www.linkedin.com/in/arunoda
On Mon, May 19, 2014 at 8:55 PM, Dan Dascalescu notifications@github.comwrote:
Ah, nevermind, I was running the app in productionhttps://github.com/meteor/meteor/wiki/Oplog-Observe-Driver#oplogobservedriver-in-production, not with meteor run, and didn't have the replica set and oplogger user set up.
— Reply to this email directly or view it on GitHubhttps://github.com/arunoda/meteor-apm-client/issues/43#issuecomment-43518326 .
Actually, there is a problem after all. I've just run the app with meteor myapp
, and according to the docs, "Oplog tailing is automatically enabled in development mode with meteor run
". The same query as above doesn't use oplog. Meteor release 0.8.0, Mongo 2.4.10, app id 6kpgrQKaEf52bsb8z.
I've enabled oplog by running mongod --master
. db.printReplicationInfo()
shows:
onfigured oplog size: 990MB log length start to end: 38196secs (10.61hrs) oplog first event time: Fri May 30 2014 05:13:09 GMT-0700 (PDT) oplog last event time: Fri May 30 2014 15:49:45 GMT-0700 (PDT) now: Fri May 30 2014 15:49:47 GMT-0700 (PDT)
Yet I still see "Not Using Oplog" in APM.
Still having the problems above, but moved the issue to the Kadira repo.
The guides on reducing network impact and response time are great.
A guide on "not using oplog", maybe even hyperlinked from the trace, would be good too.