[DOCS-6896] Recommended changes to Azure related notes Created: 04/Jan/16 Updated: 30/Nov/16 Resolved: 02/May/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | production |
| Affects Version/s: | mongodb-3.0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Steven Hand | Assignee: | Allison Reinheimer Moore |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Azure |
||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Days since reply: | 8 years, 5 weeks, 2 days ago | ||||||||||||||||
| Epic Link: | Clean Up ProdNotes | ||||||||||||||||
| Description |
|
Azure has two general types of storage, the default variant, referred to as "standard", and the "premium" storage. There are vastly different performance characteristics between this two type of storage. Building a VM with premium storage also requires the selection of specific machine types (DS and GS) and specific data centers. So, the selection of the storage type should be a significant factor in the architecture of a Azure solution that includes MongoDB (or any application that has significant performance requirements). We should update the two Azure related expositions to recommend the use of premium storage. |
| Comments |
| Comment by Steven Hand [ 11/Jan/16 ] |
|
Hi mark.benvenuto, this is a very interesting problem. I have a couple follow-up questions on your comment:
Steve |