On Fri, Jun 12, 2015 at 7:32 PM, Ian Boston <[email protected]> wrote: > Initially I was thinking about the locking behaviour but I realises 2.6.* > is still locking at a database level, and that only changes to at a > collection level 3.0 with MMAPv1 and row if you switch to WiredTiger [1].
I initially thought the same and then we benchmarked the throughput by placing the BlobStore in a separate database (OAK-1153). But did not observed any significant gains. So that approach was not pursued further. If we have some benchmark which can demonstrate that write throughput increases if we _shard_ node collection into separate database on same server then we can look further there Chetan Mehrotra
