Re: [ceph-users] Replication strategy, write throughput

2016-11-09 Thread Christian Balzer
Hello, On Wed, 9 Nov 2016 21:56:08 +0100 Andreas Gerstmayr wrote: > Hello, > > >> 2 parallel jobs with one job simulating the journal (sequential > >> writes, ioengine=libaio, direct=1, sync=1, iodeph=128, bs=1MB) and the > >> other job simulating the datastore (random writes of 1MB)? > >> > >

Re: [ceph-users] Replication strategy, write throughput

2016-11-09 Thread Andreas Gerstmayr
Hello, 2 parallel jobs with one job simulating the journal (sequential writes, ioengine=libaio, direct=1, sync=1, iodeph=128, bs=1MB) and the other job simulating the datastore (random writes of 1MB)? To test against a single HDD? Yes, something like that, the first fio job would need go again

Re: [ceph-users] Replication strategy, write throughput

2016-11-08 Thread Christian Balzer
On Tue, 8 Nov 2016 08:55:47 +0100 Andreas Gerstmayr wrote: > 2016-11-07 3:05 GMT+01:00 Christian Balzer : > > > > Hello, > > > > On Fri, 4 Nov 2016 17:10:31 +0100 Andreas Gerstmayr wrote: > > > >> Hello, > >> > >> I'd like to understand how replication works. > >> In the paper [1] several replicat

Re: [ceph-users] Replication strategy, write throughput

2016-11-07 Thread Andreas Gerstmayr
2016-11-07 3:05 GMT+01:00 Christian Balzer : > > Hello, > > On Fri, 4 Nov 2016 17:10:31 +0100 Andreas Gerstmayr wrote: > >> Hello, >> >> I'd like to understand how replication works. >> In the paper [1] several replication strategies are described, and >> according to a (bit old) mailing list post

Re: [ceph-users] Replication strategy, write throughput

2016-11-06 Thread Christian Balzer
Hello, On Fri, 4 Nov 2016 17:10:31 +0100 Andreas Gerstmayr wrote: > Hello, > > I'd like to understand how replication works. > In the paper [1] several replication strategies are described, and > according to a (bit old) mailing list post [2] primary-copy is used. > Therefore the primary OSD wa