search for: setnumsiblingthreads

...ur peak would be around 2000 logins/sec. I'm also curious if -- assuming they're well north of 2000 logins/sec -- the replication protocol begins to overwhelm the daemon at very high concurrency. Any rules of thumb on things like "For each additional 1000 logins/sec, add another # to setNumSiblingThreads and another # to setNumWorkerThreads" would be super appreciated too. Thanks! And again, feel free to point me elsewhere if there's a better place to ask. For a young project, the docs are actually quite good.

...function, then that doesn?t cause any replication. We?ve tested with three servers, each handling around 5-6000 logins/sec (i.e. 15-18K requests each) and the overall query rate was maintained. > Any rules of thumb on things like "For each additional 1000 logins/sec, add > another # to setNumSiblingThreads and another # to setNumWorkerThreads" > would be super appreciated too. > Actually the rule of thumb is more like: - WorkerThreads - Set to number of CPUs. Set number of LuaContexts to WorkerThreads + 2 - SiblingThreads - Leave at 2 unless you see issues. > Thanks! And again, feel...

I've been playing with weakforced, so it fills in the 'fail2ban across a cluster' niche (not to mention RBLs). It seems to work well, once you've actually read the docs :) I was curious if anyone had played with it and was *very* curious if anyone was using it in high traffic production. Getting things to 'work' versus getting them to work *and* handle a couple hundred