Performance impact of using Readonly Protection in production

[Joyce Babu]

What is the performance impact of using readonly protection in production? Is it recommended to enable it in production environment?

Readonly protection is set to 'On' on my server, but xcache_mmap is set to /dev/zero. Should I change mmap path to /tmp/xcache for readonly protection to take effect?

[xcache]

On Fri, Jan 4, 2013 at 10:32 PM, Joyce Babu <jo...@joycebabu.com> wrote:
> What is the performance impact of using readonly protection in production?
> Is it recommended to enable it in production environment?

"shallow copy optimization" cannot be applied when readonly protection
is on. "deep copy" is used instead and is a little bit slower

this protection is for any bug in XCache+Zend combination that may
corrupt the cache. instead of corrupting cache silently, the readonly
protection ensure it crash so you know bad thing going and it can be
reported back to XCache dev to figure out the reason and fix it. if
you feel it stable after running a while, you can disable it for
performance

>
> Readonly protection is set to 'On' on my server, but xcache_mmap is set to
> /dev/zero. Should I change mmap path to /tmp/xcache for readonly protection
> to take effect?

yes
>
> --
>
>
>