Re: Forcing enabling/disabling of journal file pre-allocation
To be more specific, I have 2 drives:
Drive 1 = SAS drive
Drive 2 = SATA drive
mongo data is on drive 2. When I run with the journal directory on
drive 2, the journal files are never preallocated. When I set up a
junction to map the journal directory on to drive 1 instead, it always
preallocates the journal files there. So when performance testing the
difference of having the journals on the same or separate disks, I
can't seem to get a common baseline to start from.
On Mar 18, 8:27 am, AdaTheDev <adathe...@...> wrote:
> Is it possible to control whether or not mongodb preallocates journal
> I'm just running some tests to get some performance benchmarks of
> journaling, and the first time I started mongodb with --journal it
> didn't preallocate the journal files, subsequent times it has
> preallocated them.
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To post to this group, send email to mongodb-user@...
To unsubscribe from this group, send email to mongodb-user+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/mongodb-user?hl=en.