Kadira

This guide will help you get started with Kadira to identify how your app behaves and help you take necessary actions.

This is a general guide that can be used to optimize the response time of your methods and publications.

Publications are the main place where your app sends data to the client. You can follow simple techniques on reducing PubSub data usage and reduce server memory usage and latency very easily.

If you could be able to reuse observers, you will be able to save higher CPU and Network Utilization. First understand the concept and apply into your app.

Meteor caches a lot of data in the memory. You need to understand how that affects your app and what are the solutions if your app is affected.

Iron Router normally unsubscribes all previous subscriptions when entering into a new route. Because of this your CPU and Bandwidth will be wasted.

Meteor supports most of the queries with oplog, but there are some edge cases where observers will fall back into an inefficient poll and diff implementation. Let me show you those edge cases.

If you've ever looked at a Kadira trace, you should've seen the waitTime. In this article, I'll explain to you about the waitTime and how you can manage it.

If you need to see what exactly is happening inside your app, the best option is to take a CPU profile. It is not easy to take and analyze a CPU profile with NodeJS; we need the right set of tools and guides, which is what we are doing with Kadira's CPU profiler.

Let's learn how to analyze a CPU profile

Observers are among the key components of Meteor. They take care of observing documents on MongoDB and they notify changes. Let's see how you can monitor them with Kadira.

With Kadira Insights, you can find relationships in your app. Then you can try to predict and plan your app accordingly.