On Mon, Sep 21, 2015 at 8:51 AM, Trey Jones <tjones(a)wikimedia.org> wrote:
That's very cool! Have you stress-tested it at
all? Like, what happens if
you search 10 wikipedias at once? (Because you know I want to search 10
wikis at once. <g>)
No issues with a dozen requests at once in the application layer. Our
cluster on the other hand may not be as happy :) We will have to figure
out how to manage the load this feature could generate.
On Mon, Sep 21, 2015 at 12:56 PM, Stas Malyshev <smalyshev(a)wikimedia.org>
wrote:
Cool! I wonder if there's any interaction with the pool counters search
is using. I.e. would it block on pool counter, use one counter for all
async work, etc.
Good question. Pool counter is very picky about how you can nest locks. It
actually rejected any attempt to nest locks until nik changed it for the
purposes of allowing us to nest the regular lock inside of a per-user lock.
I'm not sure how we will want to move forward here, something to think
about.