<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Benchmark on Ubuntu Tips</title><link>https://ubuntips.com/tags/benchmark/</link><description>Recent content in Benchmark on Ubuntu Tips</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sat, 21 Nov 2026 15:21:28 +0800</lastBuildDate><atom:link href="https://ubuntips.com/tags/benchmark/index.xml" rel="self" type="application/rss+xml"/><item><title>XenForo on Valkey: do you need php-redis?</title><link>https://ubuntips.com/posts/xenforo-valkey-php-redis-vs-sv-rediscache/</link><pubDate>Sat, 21 Nov 2026 14:45:00 +0800</pubDate><guid>https://ubuntips.com/posts/xenforo-valkey-php-redis-vs-sv-rediscache/</guid><description>&lt;p&gt;XenForo can store its cache in Redis or Valkey in two ways. The core provider needs the &lt;code&gt;php-redis&lt;/code&gt; extension. The popular SV RedisCache add-on ships its own pure-PHP client (Credis) and works with no extension at all. I wanted to know whether &lt;code&gt;php-redis&lt;/code&gt; is worth making a hard requirement for every XenForo server, so I measured it.&lt;/p&gt;&#10;&lt;p&gt;Short answer: no. On the forum, thread and mixed pages the two clients are within about 2% of each other, with the database on the same box or on a simulated remote server. The only larger gaps came from single noisy rounds, and they favoured the pure-PHP client. What matters is that the cache is on, and that the SV add-ons are installed.&lt;/p&gt;</description></item></channel></rss>