Olivier, Can you correlate anything like GC pauses with these slow deliveries?
-- Mike Stolz Principal Engineer, GemFire Product Lead Mobile: +1-631-835-4771 On Fri, Jan 11, 2019 at 1:36 PM Anilkumar Gingade <[email protected]> wrote: > Oliv, > > The subscription has cost associated with it; as interested need to be > processed for all the clients; but its minimal looking for matching > keys/regex. > - The puts add the matched events to the client subscription queues on the > server; do you see the client queues growing? > - You may also need to see if there are any memory pressure on server. > - If the clients are not consuming the events fast (slow clients) it may > increase the server side queue size. > > -Anil. > > > On Fri, Jan 11, 2019 at 8:56 AM Olivier Mallassi < > [email protected]> wrote: > >> sorry mistake : throughtput is 10 times less: 5k requests per sec. >> >> On Fri, Jan 11, 2019 at 5:44 PM Olivier Mallassi < >> [email protected]> wrote: >> >>> All >>> >>> I am facing a kind of scaling mystery while using register interest. >>> >>> Use-case is basic : >>> N publishers publishing into a geode cluster w/ M subscribers using >>> register_interest (regexp). >>> >>> in our case, >>> - M can be up to 1000 process (not threads) >>> - Publisher throughput is about 50k requests per sec on 200k keys >>> - Volume is small (around 10GB) >>> >>> We observe put (from publisher point of view) latency diverging with the >>> number of consumers, up to 10 sec (p99) and 5 sec (p50) >>> AFAIR, the key is evaluated on the put (sync). >>> >>> Any ideas , customisation of the configuration you can advice? >>> >>> Regards. >>> >>> Oliv/ >>> >>
