GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Embed Notice

HTML Code

Corresponding Notice

  1. Embed this notice
    feld (feld@friedcheese.us)'s status on Friday, 20-Jun-2025 11:30:52 JSTfeldfeld
    in reply to
    • wuhan.bat™
    @jae yeah I prefer valkey. The benchmarks aren't a lie, traditional Redis is single threaded which is obviously problematic if you care about it ever being able to use more than 1 CPU core

    However, pinning the work to one core means you have a better chance of the kernel / NUMA implementation allocating memory on the local memory controller which will keep the memory accesses as low latency as possible

    With Valkey it's possible it needs to read from memory attached to another CPU and that could be significant under heavy load

    Well, guess that just means if you're trying to use all your hardware for a busy Redis workload you need to be smart about the hardware you pick

    Trade offs... but normal multi core CPUs on a single socket motherboard? Should smoke Redis
    In conversationabout 2 days ago from friedcheese.uspermalink
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.