2014 04 28 improvements for the meteor apm client - giordanocardillo/kadira-server GitHub Wiki
layout: blog_post title: Improvements For The Meteor APM Client category: product summery: Last week, we spent some time optimizing the Meteor APM client package and adding some useful features. Here are the improvements we did.
Last week, we spent some time optimizing the Meteor APM client package and adding some useful features.
We were able to reduce the Meteor APM client's CPU usage, which is now negligible.
Simply update your Meteor APM client package with
mrt updateto benefit the CPU improvements.
Now we've added a few useful features to help you to identify the root causes of performance problems or bugs very easily.
Now when you are looking at a Method or PubSub trace, you can view the params you've sent along with it. You can use that information to identify the root cause:
If one of your DB operations is slow, it is very important to find the number of documents fetched. Similarly, if you are invoking an update or remove operation, it is valuable to get the number of documents affected by that operation. Now you can check these numbers with Meteor APM:
When you've returned a cursor from a publication, Meteor applies an observeChanges operation on it. If there is a cached observer based on the same query and options, Meteor will reuse it. You can now identify that with Meteor APM:
This shows that noOfHandles is greater than one. This means you are utilizing the cache and the data is not fetched again from the DB.
And also, you can see the number of documents the cache contains. All these documents will be sent to the client eventually.
To get all these new features, simply update the Meteor APM client package with
mrt updateand deploy your app again.