On Tue, Mar 22, 2016 at 4:48 PM, Jason Dillaman wrote:
>> Hi Jason,
>>
>> Le 22/03/2016 14:12, Jason Dillaman a écrit :
>> >
>> > We actually recommend that OpenStack be configured to use writeback cache
>> > [1]. If the guest OS is properly issuing flush requests, the cache will
>> > still provi
> Hi Jason,
>
> Le 22/03/2016 14:12, Jason Dillaman a écrit :
> >
> > We actually recommend that OpenStack be configured to use writeback cache
> > [1]. If the guest OS is properly issuing flush requests, the cache will
> > still provide crash-consistency. By default, the cache will automaticall
Hi Jason,
Le 22/03/2016 14:12, Jason Dillaman a écrit :
We actually recommend that OpenStack be configured to use writeback cache [1].
If the guest OS is properly issuing flush requests, the cache will still
provide crash-consistency. By default, the cache will automatically start up
in wr
> > I've been looking on the internet regarding two settings which might
> > influence
> > performance with librbd.
> >
> > When attaching a disk with Qemu you can set a few things:
> > - cache
> > - aio
> >
> > The default for libvirt (in both CloudStack and OpenStack) for 'cache' is
> > 'none'. I
Hi Wido,
Le 22/03/2016 13:52, Wido den Hollander a écrit :
Hi,
I've been looking on the internet regarding two settings which might influence
performance with librbd.
When attaching a disk with Qemu you can set a few things:
- cache
- aio
The default for libvirt (in both CloudStack and OpenSt
Hi,
I've been looking on the internet regarding two settings which might influence
performance with librbd.
When attaching a disk with Qemu you can set a few things:
- cache
- aio
The default for libvirt (in both CloudStack and OpenStack) for 'cache' is
'none'. Is that still the recommend value