Has anyone done any real testing of Redis as a bayes backend? Talking
with one of our customer, with a trivial <60,000 accounts, they are
seeing:
  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+ COMMAND
22452 redis 20 0 28.7g 28g 740 S 9.6 72.4 1139:38 redis-server
28GB purely for a bayes DB for < 60k accounts is insanity.

could you please post your "# Memory"  section of
"redis-cli info"

Also note that redis server cannot return allocated memory back to the
system. If its virtual memory usage grew high due to some temporary
peak needs or misconfiguration, the 'memory section' of "redis-cli info"
will report low usage but process virtual memory will remain high.

In such case the solution is to restart redis daemon - it will re-read
its database data from its last snapshot dump (provided that snapshotting
is not disabled).

  Mark

Reply via email to