Compatibility with Object Cache Pro (OCP)

We are trialing OCP and wish to know whether it is compatible with dragonfly.
Our hosting provider has brought our attention to Dragonfly, but they are not sure whether Dragonfly as a drop in for redis, can be used OCP.
and the Igbinary and ZSTD Compression. Please confirm the position. Many thanks

PS we are on Cloudlinux solo set up - 2 dedicated server set up main and remote db.

do you use client side caching?

do you use Relay as a client or something else?

At the moment we are just using PhpRedis 5.3.7 and Redis 5.0.3. We are using cloudlinx OS and the PHP prerequisites are not in place to use Relay yet… They will provide the same in the next couple of weeks as an update. In teh mean time we also wanted to test Object Cache Pro with Dragonfly and see which one works best for us also from a pricing point of view. The OCP chap has confirmed that it will work. We just have to know whether it will all work on cloudlinux solo - Server architecture Linux 4.18.0-477.13.1.lve.1.el8.x86_64 x86_64

You will need to build Dragonfly from source (and it should work) to run a native binary or alternatively run containers. To the best of my knowledge, Dragonfly works with kernel 4.18

hosting and cloudlinux say it won’t work on the 4.18 kernel. So waiting to see when cloudlinux 9 is released so that incomcmpatibility issue will eb resolved - shame I was lloking forwatrd to testing this out

Moved to ubuntu 22.04 Pro and finally testing out various combinations in memory caching set up. I have tried object cache pro (OCP) and Relay, and would now like to try dragonflydb with object cache pro. There are certain php extensions and compressions that need to compiled with PhpRedis: (i) igbinary (ii) lz4; (iii) zstd. does dragonfly support this?

I had initially thought that I could also use Relay(as the PHPRedis) Dragonflydb and OCP, but I understand that - Dragonfly does not support Redis RESPv3, and thus Relay will not work with Dragonfly.

Please addres the two points

Dragonfly supports resp3 . It does not support client side caching

so if Relay is used as PHPredis only, which is a config option, can you see Dragonflydb/cbject cache pro/Relay as php redis being a viable combination. I would like to test this but do not wsh to crash the site

How do you run redis? What’s the config/arguments?

@inclusive-numbat Hi there Roman. I was wondering if you can continue your guidance on my query. Thanks!!

We have not tried running Dragonfly with Relay ourselves but we do support all the commands it probably uses. The open question is how redis is configured when it runs with Relay and your answers did not fully covered it.

You can fetch them by directly connecting to redis and running “config get *”

this is from the author of Relay. Is this still the case: Last time I checked DragonflyDB does not support CLIENT TRACKING which is part of RESP3 and required to by Relay.

yes, this was my first question

We have not implemented it yet

I have just obtained the config details it runs to 390 lines! Sorry to be off the mark here, what are yiu looking for by way of an entry. Can you provide an example then I will extract what is relevant.

To your point yes I also understand that Relay and Dragonfly cannot work together with relay in full mode. However, it can be configured to replace phpRedis and not to use teh Cache feature. That is what I wanted to try out.

And do you envisage adding the Client Tracking feature any time soon