Capacity Planning

Editor's Notes

1. Fine art of translating Requirements of the application into resources needed to support the application that implements those requirements
2. Fine art of translating Requirements of the application into resources needed to support the application that implements those requirements
3. Understanding the requirements and resources implication
4. Collection scans
5. These numbers are already old and not relevant anymore.
6. These numbers are already old and not relevant anymore.
7. These numbers are already old and not relevant anymore.
8. These numbers are already old and not relevant anymore.
9. MongoDB Ops Manager can do a lot for [ops teams]. Best Practices, Automated. Ops Manager takes best practices for running MongoDB and automates them. So you run ops the way MongoDB engineers would do it. This not only makes it more fool-proof, but it also helps you… Cut Management Overhead. No custom scripting or special setup needed. You can spend less time running and managing manual tasks because Ops Manager takes care of a lot of the work for you, letting you focus on other tasks. Meet SLAs. Automating critical management tasks makes it easier to meet uptime SLAs. This includes managing failover as well as doing rolling upgrades with no downtime. Scale Easily. Provision new nodes and systems with a single click.
10. Ops Manager agents are installed on servers (where MongoDB will be deployed), either through configuration tools such as Chef or Puppet, or by an administrator. The administrator creates a new design goal for the system, either as a modification to an existing deployment (e.g., upgrade, oplog resize, new shard), or as a new system. The agents periodically check in with the Ops Manager central server and receive the new design instructions. Agents create and follow a plan for implementing the design. Using a sophisticated rules engine, agents continuously adjust their individual plans as conditions change. In the face of many failure scenarios – such as server failures and network partitions – agents will revise their plans to reach a safe state. Minutes later, the system is deployed – safely and reliably.
11. Ops Manager monitors 100+ metrics that could impact the performance of your database Track key performance indicators across dozens of optimized charts Build customized alerts that trigger when metrics are out of range; have them delivered how you want
12. RESTful API to monitor MongoDB alongside the rest of your application infrastructure, from a single “pane of glass” Packaged integrations with leading APM platforms such as New Relic now available with MongoDB Cloud Manager
13. Quickly identify your slow-running queries. Part of MongoDB Ops Manager, the Visual Query Profiler displays how query and write latency vary over time With the click of a button, the Visual Query Profiler consolidates and displays metrics from all your nodes on a single screen
14. The Visual Query Profiler analyzes the data it displays and presents recommendations for new indexes that can be created to improve the performance of your deployment.
15. The best practice for adding new indexes to your deployment is a rolling index build – starting with each of the secondaries and finally applying changes to the original primary, after swapping its role with one of the secondaries. Ops Manager can automate this process across your replica sets, reducing your operational overhead and the risk of failovers caused by incorrectly sequencing management processes.
16. Ops Manager coordinates and orchestrates critical operational tasks across the servers in a MongoDB system. Tasks that you would have otherwise performed manually, such as… Deploying a new cluster Upgrades Adding capacity Database restores Use the Ops Manager UI directly, or invoke the Ops Manager RESTful API from your existing enterprise orchestration frameworks, such as Chef, Puppet, etc.
17. Restore to precisely the moment you need, quickly and safely. Ops Manager is the only MongoDB backup solution that offers point-in-time backups of replica sets and cluster-wide snapshots of sharded clusters. Integrates with standard network-mountable file systems Backups can be configured against specific collections, rather than the entire database