<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Redis on KeyValueStore.com</title>
    <link>https://keyvaluestore.com/tags/redis/</link>
    <description>Recent content in Redis on KeyValueStore.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 05 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://keyvaluestore.com/tags/redis/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Keyspace Map Shows What a Redis or Valkey Keyspace Holds, From a Plain SCAN Key List</title>
      <link>https://keyvaluestore.com/keyspace-map-shows-what-a-redis-or-valkey-keyspace-holds-from-a-plain-scan-key-list/</link>
      <pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://keyvaluestore.com/keyspace-map-shows-what-a-redis-or-valkey-keyspace-holds-from-a-plain-scan-key-list/</guid>
      <description>&lt;p&gt;A key-value store has no tables and no schema to read. Everything sits in one flat list of keys, and the only structure is whatever people built into the names. After a few years and a few teams, the honest answer to &amp;ldquo;what&amp;rsquo;s in our Redis?&amp;rdquo; is often a shrug.&lt;/p&gt;&#xA;&lt;p&gt;The &lt;a href=&#34;https://keyvaluestore.com/tools/keyspace/&#34;&gt;Keyspace Map&lt;/a&gt; reads that structure back out of the names. Paste the output of &lt;code&gt;redis-cli --scan&lt;/code&gt; or &lt;code&gt;valkey-cli --scan&lt;/code&gt;, and a long key list becomes a short list of patterns with counts. In one test, 9,161 keys came down to 13 lines, led by &lt;code&gt;user:&amp;lt;id&amp;gt;:profile&lt;/code&gt; with 3,000 keys, &lt;code&gt;user:&amp;lt;id&amp;gt;:settings&lt;/code&gt; with 2,000 and &lt;code&gt;session:&amp;lt;hex&amp;gt;&lt;/code&gt; with 1,500. The same keys show as a tree of prefixes you can open level by level, with how many bytes the key names take.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Mass Insert Builder Turns CSV and JSON Into a Bulk-Load File for Redis and Valkey</title>
      <link>https://keyvaluestore.com/mass-insert-builder-turns-csv-and-json-into-a-bulk-load-file-for-redis-and-valkey/</link>
      <pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://keyvaluestore.com/mass-insert-builder-turns-csv-and-json-into-a-bulk-load-file-for-redis-and-valkey/</guid>
      <description>&lt;p&gt;The slow way to load a million keys into Redis or Valkey is a loop that sends a command, waits for the answer, and sends the next. Most of the time goes on the waiting. At half a millisecond per round trip, a million commands take more than eight minutes before the server has done anything hard.&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt;redis-cli --pipe&lt;/code&gt; and &lt;code&gt;valkey-cli --pipe&lt;/code&gt; skip the wait. They stream commands as fast as the connection takes them, read the replies as they arrive, and end with a count: &lt;code&gt;errors: 0, replies: 1000000&lt;/code&gt;. The catch is that they want their input already in the Redis protocol, where every value is preceded by its length in bytes. The &lt;a href=&#34;https://keyvaluestore.com/tools/pipe/&#34;&gt;Mass Insert Builder&lt;/a&gt; writes that file for you.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Snapshot Viewer Opens Redis and Valkey RDB Snapshots in the Browser, From Redis 2.8 to Valkey 9.1</title>
      <link>https://keyvaluestore.com/snapshot-viewer-opens-redis-and-valkey-rdb-snapshots-in-the-browser-from-redis-2.8-to-valkey-9.1/</link>
      <pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://keyvaluestore.com/snapshot-viewer-opens-redis-and-valkey-rdb-snapshots-in-the-browser-from-redis-2.8-to-valkey-9.1/</guid>
      <description>&lt;p&gt;A Redis server is using 40 GB and nobody is sure what&amp;rsquo;s in it. The usual tools all ask the server itself. &lt;code&gt;--bigkeys&lt;/code&gt; scans every key, &lt;code&gt;MEMORY USAGE&lt;/code&gt; asks about one key at a time, and a script over &lt;code&gt;SCAN&lt;/code&gt; adds its own load to a machine that&amp;rsquo;s already the busiest in the building.&lt;/p&gt;&#xA;&lt;p&gt;There&amp;rsquo;s a copy of the same data that answers those questions for free: the snapshot. The &lt;a href=&#34;https://keyvaluestore.com/tools/snapshot/&#34;&gt;Snapshot Viewer&lt;/a&gt; opens a &lt;code&gt;dump.rdb&lt;/code&gt; in your browser and shows the keys by type and database, the biggest keys, the prefixes that take the most space, how long expiring keys have left, and the value of any key you pick.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Traffic Analyzer Turns Redis and Valkey MONITOR Output Into a Cache Hit-Rate Curve That Matched a Real Server</title>
      <link>https://keyvaluestore.com/traffic-analyzer-turns-redis-and-valkey-monitor-output-into-a-cache-hit-rate-curve-that-matched-a-real-server/</link>
      <pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://keyvaluestore.com/traffic-analyzer-turns-redis-and-valkey-monitor-output-into-a-cache-hit-rate-curve-that-matched-a-real-server/</guid>
      <description>&lt;p&gt;A Redis server is running hot and the question is what with. &lt;code&gt;INFO commandstats&lt;/code&gt; counts commands but can&amp;rsquo;t say which keys or which clients. The slow log only keeps the slow ones. &lt;code&gt;MONITOR&lt;/code&gt; shows everything, every command with its keys and the address that sent it, but at 30,000 lines a second nobody reads it.&lt;/p&gt;&#xA;&lt;p&gt;The &lt;a href=&#34;https://keyvaluestore.com/tools/traffic/&#34;&gt;Traffic Analyzer&lt;/a&gt; reads a &lt;code&gt;MONITOR&lt;/code&gt; capture in your browser and adds it up: commands per second, the command mix, reads against writes, the busiest keys and key patterns, which clients send what, how the keys would spread over a cluster, commands worth a second look, and how many keys a cache would need to hold.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
