https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7014
--- Comment #7 from peter gervai <[email protected]> --- (In reply to Henrik Krohns from comment #6) > (In reply to peter gervai from comment #5) > > and probably I have to ditch redis when I move > > over per-user-configs (unless mr. author prefix the keys with userid and > > solve the problem, don't ask me why he haven't). > > Probably because you do not want n^2 users each using 1GB of memory for > tokens? Well even if you have n^2 users then you probably don't have much choice apart from storing the data you need. I'm not familiar with redis, so this is only educated guessing: if you believe you'll have more tokens than users (which seems to be a good assumption) I guess the way to go could be: HMSET w:token1 user:bob:spam 55432 user:bob:ham 23 HMSET w:token1 u:joe:s 22 u:joe:h 8171091 HMSET w:token1 u:henrik:s 86373 u:henrik:h 832 But I guess this will _not_ help fixing psql locking problems, only avoiding it. :-( -- You are receiving this mail because: You are the assignee for the bug.
