Would you change Redis for Dragonfly?

Lately I've been testing our docker stacks defining self containing web applications (no shared database or cache), they are relatively small applications (a GLPi instance with about 1000 users being the largest).

I have found that Dragonfly (which should be significantly faster than Redis on non clustered configurations) is genuinely plug and play in such scenarios.

For context. Dragonfly is a KV DB that has a Redis compatibility mode, and it's supposedly much faster in non clustered configurations as it doesn't depend as much on clustering to scale.

Personally, I'm intrigued by realizing possible performance gains, even if they are only visible under load, and it can be hot-swapped by replacing a single line inside the container definition (docker-compose or quadlet in this case). But I'm worried about side effects. I have already seen that it expect certain amount of RAM be available per core, which my test VM didn't care much for, but limiting the number of threads is easy.

Anyone out there with relevant experience?