[MarkLogic Dev General] SSD and fast data directory
Gary.Russo at marklogic.com
Tue Oct 1 19:31:46 PDT 2013
>> I realize this may depend on exactly *how* fast of an SSD and HDD, but are there any rules of thumb (or exceptions to look out for)?
As you say, it all depends on the quality of the SSD and HDD.
I don't know of any rule of thumb but this write up may be useful. => http://www.storagereview.com/marklogic_nosql_database_storage_benchmark
The write up compares storage options using latency instead of throughput (MB/sec).
As you'd expect, the latency of the HDD storage systems tested have much higher latency than the SSD systems.
Professional Services Media Consultant
From: general-bounces at developer.marklogic.com [mailto:general-bounces at developer.marklogic.com] On Behalf Of Will Thompson
Sent: Tuesday, October 1, 2013 7:20 PM
To: MarkLogic Discussion
Subject: [MarkLogic Dev General] SSD and fast data directory
The example in ML's docs suggest an 8-core server with 4 forests, all sharing one SSD fast data directory. Is it fair to assume that even under heavy load the single-threaded speed of an SSD will always outperform the
4 forests of magnetic disks? It seems like there might be scenarios where having multiple IO threads would be beneficial, even if they're not SSD speeds. I realize this may depend on exactly *how* fast of an SSD and HDD, but are there any rules of thumb (or exceptions to look out for)?
Also, assuming you could fit your entire database on an SSD, what differences are there between putting the forest directly on the SSD vs putting it on HDDs with the fast data directory configured on the SSD?
General mailing list
General at developer.marklogic.com
More information about the General