Run MongoDB on Arm-based Azure Cobalt 100 instances
Introduction
What are Cobalt 100 and MongoDB?
Create an Arm-based cloud virtual machine using Cobalt 100
Install MongoDB and Mongosh
MongoDB Baseline Testing
Monitor MongoDB with mongotop
Monitor MongoDB with mongostat
Monitor MongoDB with mongostat
Next Steps
Run MongoDB on Arm-based Azure Cobalt 100 instances
Who is this for?
This is an introductory topic for software developers who want to migrate MongoDB workloads to Arm-based platforms, with a focus on Microsoft Azure Cobalt 100 Arm64 instances.
What will you learn?
Upon completion of this Learning Path, you will be able to:
- Provision an Arm64-based VM in Azure that's powered by Cobalt 100 and uses Ubuntu Pro 24.04 LTS.
- Deploy MongoDB on the Cobalt 100-based instance.
- Run baseline tests and performance benchmarks on MongoDB in the Arm64 environment.
Prerequisites
Before starting, you will need the following:
- A Microsoft Azure account with access to Cobalt 100-based instances (Dpsv6)
- Familiarity with the MongoDB architecture and deployment practices on Arm64 platforms
Summary
This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
mongosh, and configure mongod for local access. You’ll validate CRUD, indexing, concurrency, and storage behavior with mongosh and fio. Finally, you’ll generate load and use mongotop to observe per-collection read and write activity in real time.Frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
mongod locally and confirm that it binds to 127.0.0.1. Connect with mongosh, run the service health checks, and review the MongoDB log for errors.mongod remains bound to 127.0.0.1. Before you accept remote connections, set --bind_ip or bindIp, create users, and enable authorization.mongod is bound to 127.0.0.1, long_system_load.js is generating traffic in another terminal, and the MongoDB Database Tools are installed. Run mongotop while the workload is active.fio completes without errors and that your CRUD, index, and concurrency checks succeed in mongosh. While the workload runs, mongotop should update per-collection read and write times in real time.