Details
-
Bug
-
Resolution: Won't Fix
-
Minor - P4
-
None
-
*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
*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
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