[DOCS-4641] Comment on: "mongodb-ecosystem/platforms/google-compute-engine.txt" Created: 11/Jan/15  Updated: 11/Jan/17  Resolved: 27/Jul/16

Status: Closed
Project: Documentation
Component/s: ecosystem
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Bug Priority: Minor - P4
Reporter: Docs Collector User (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: http://docs.mongodb.org/ecosystem/platforms/google-compute-engine/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.95 Safari/537.36
Referrer: http://docs.mongodb.org/ecosystem/platforms/google-compute-engine/
Screen Resolution: 1440 x 900
repo: docs-ecosystem
source: platforms/google-compute-engine


Participants:
Days since reply: 7 years, 29 weeks ago

 Description   

GCE offers persistent disk storage to go along with your instances, either as a single root volume or with multiple disks attached to an instance. GCE’s persistent disks (PD) already stripe data across a very large number of volumes, SHERE is no need to do it yourself. MongoDB journal data is small and putting it on its own disk means either creating a small disk with insufficient performance or creating a large disk that goes mostly unused. Put your MongoDB journal files on the same disk as your data. Putting your MongoDB journal files on a small persistent disk will dramatically decrease performance of database writes.

SHERE should where there



 Comments   
Comment by Kay Kim (Inactive) [ 27/Jul/16 ]

subsumed under other ecosystem work.

Generated at Thu Feb 08 07:48:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.