Hey Pedro, > > 1) What is the default bundler used in JGroups 2.7.x? > > Bela is the right person to answer this, but I think the new bundler was > created only in JGroups 3.3.x.
So what happens if the JGroups 2.7.x config file has UDP.bundler_type="new"? Will it just be ignored? Thanks, Alan ----- Original Message ----- > From: "Pedro Ruivo" <[email protected]> > To: [email protected] > Sent: Wednesday, June 5, 2013 9:47:51 AM > Subject: Re: [infinispan-dev] Infinispan 5.3 and the new JGroups bundler > > Hi Alan, > > On 06/05/2013 02:43 PM, Alan Field wrote: > > Hey Pedro, > > > > I have a couple of questions for you about this. > > > > 1) What is the default bundler used in JGroups 2.7.x? > > Bela is the right person to answer this, but I think the new bundler was > created only in JGroups 3.3.x. > > > > > 2) Are there any issues with running versions of Infinispan < 5.3 with the > > new bundler? > > No problem at all. In Infinispan < 5.3 the priority/synchronous messages > (puts, prepares, commits, remote gets, etc...) bypass the bundling > mechanism and they are sent to the network immediately. > > Cheers, > Pedro > > > > > Thanks, > > Alan > > > > ----- Original Message ----- > >> From: "Pedro Ruivo" <[email protected]> > >> To: "ispn-dev" <[email protected]> > >> Sent: Tuesday, June 4, 2013 10:12:49 AM > >> Subject: [infinispan-dev] Infinispan 5.3 and the new JGroups bundler > >> > >> Hi all, > >> > >> In Infinispan 5.3 we are allowing message bundling due to "recent" > >> improvements made in JGroups' bundler. > >> > >> The new bundler is the default in JGroups 3.3 but if you are using the > >> old bundler (UDP.bundler_type="old"), please may consider to change it > >> to use the new bundler (UDP.bundler_type="new"). > >> > >> If you don't want to change it, please consider that the old bundler can > >> lead a performance degradation in a low throughput system (when you have > >> 1 or 2 threads performance operations). Note that, in the old blunder, > >> the messages are blocked until (default values, of course you can > >> tunning this values to match to your application): > >> > >> * 30 milliseconds are expired; > >> or > >> * 64k bytes are ready to be sent. > >> > >> Recall that this warning is valid for Infinispan 5.3 (and superior in > >> the future). > >> > >> Thank You. > >> > >> Regards, > >> Pedro Ruivo > >> _______________________________________________ > >> infinispan-dev mailing list > >> [email protected] > >> https://lists.jboss.org/mailman/listinfo/infinispan-dev > >> > > _______________________________________________ > > infinispan-dev mailing list > > [email protected] > > https://lists.jboss.org/mailman/listinfo/infinispan-dev > > > _______________________________________________ > infinispan-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/infinispan-dev > _______________________________________________ infinispan-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/infinispan-dev
