Re: [infinispan-dev] Distributed Counter Discussion

On Tue, Mar 22, 2016 at 7:12 PM, Bela Ban wrote: > > > On 22/03/16 18:04, Dan Berindei wrote: >> On Mon, Mar 21, 2016 at 1:43 PM, Bela Ban wrote: >>> >>> >>> On 21/03/16 11:12, Pedro Ruivo wrote: Hi all, @Eric, thanks for the requirements.

Re: [infinispan-dev] Distributed Counter Discussion

On 22/03/16 18:04, Dan Berindei wrote: > On Mon, Mar 21, 2016 at 1:43 PM, Bela Ban wrote: >> >> >> On 21/03/16 11:12, Pedro Ruivo wrote: >>> Hi all, >>> >>> @Eric, thanks for the requirements. >>> >>> @Bela, does JGroups counter supports that semantics (AP)? >> >> No. You'd

Re: [infinispan-dev] Distributed Counter Discussion

On Mon, Mar 21, 2016 at 1:43 PM, Bela Ban wrote: > > > On 21/03/16 11:12, Pedro Ruivo wrote: >> Hi all, >> >> @Eric, thanks for the requirements. >> >> @Bela, does JGroups counter supports that semantics (AP)? > > No. You'd have to catch the MergeView and do this manually. I

Re: [infinispan-dev] Google load balancer design

On Tue 2016-03-22 8:56, Radim Vansa wrote: > On 03/22/2016 08:24 AM, Emmanuel Bernard wrote: > > http://blog.acolyer.org/2016/03/21/maglev-a-fast-and-reliable-software-network-load-balancer/ > > > > Interesting read. Some data points I extracted. > > > > 350 ns per parquet. Ensuring a 300us

Re: [infinispan-dev] Google load balancer design

On 03/22/2016 08:24 AM, Emmanuel Bernard wrote: > http://blog.acolyer.org/2016/03/21/maglev-a-fast-and-reliable-software-network-load-balancer/ > > Interesting read. Some data points I extracted. > > 350 ns per parquet. Ensuring a 300us during load. Regrettably JGroups does not bypass Linux

[infinispan-dev] Google load balancer design

http://blog.acolyer.org/2016/03/21/maglev-a-fast-and-reliable-software-network-load-balancer/ Interesting read. Some data points I extracted. 350 ns per parquet. Ensuring a 300us during load. Some math I was not aware of: [quote] -- Let N be the size of a VIP’s backend pool. A table is