Hi Ted, that is interesting to hear. Thanks for the advice/recommendation. We have also started to use unsettled deliveries (AT_LEAST_ONCE in vertx-proton) but still are not able to get more than 2000 - 3000 messages/sec throughput :-( We will strip everything down to the bare minimum and then post our setup, i.e. sender/receiver code and Dispatch Router config.
BTW We are running Dispatch Router by means of the enmasseproject/qdrouterd-base:0.8.0-1 Docker image. Do you have any concerns regarding a negative impact this might have on throughput? Mit freundlichen Grüßen / Best regards Kai Hudalla Chief Software Architect Bosch Software Innovations GmbH Schöneberger Ufer 89-91 10785 Berlin GERMANY www.bosch-si.com Registered office: Berlin, Register court: Amtsgericht Charlottenburg, HRB 148411 B; Executives: Dr.-Ing. Rainer Kallenbach, Michael Hahn ________________________________________ From: Ted Ross <tr...@redhat.com> Sent: Monday, July 17, 2017 20:16 To: users@qpid.apache.org Subject: Re: Dispatch Router throughput When doing throughput benchmarking, I would strongly recommend using unsettled deliveries. With pre-settled deliveries, there is no effective end-to-end flow control. If there is congestion (senders faster than receivers), the router will aggressively discard excess pre-settled deliveries. If you use unsettled deliveries, the router will be able to provide smooth end-to-end flow control. It is my understanding from the benchmarking that we have done that unsettled deliveries perform as well or better than pre-settled deliveries. -Ted On Mon, Jul 17, 2017 at 3:23 AM, Hudalla Kai (INST/ECS4) < kai.huda...@bosch-si.com> wrote: > Thanks everybody for your help with this problem. I think that we will > first need to isolate the problem further down to the lower layers. > Currently, there are too many components involved AFAIC. We will now first > create a test client just based on vertx-proton in order to rule out our > Hono specific code on top of it. > > We will come back with the outcome of this once we have run some tests > using the plain client. > > Mit freundlichen Grüßen / Best regards > > Kai Hudalla > Chief Software Architect > > Bosch Software Innovations GmbH > Schöneberger Ufer 89-91 > 10785 Berlin > GERMANY > www.bosch-si.com > > Registered office: Berlin, Register court: Amtsgericht Charlottenburg, HRB > 148411 B; > Executives: Dr.-Ing. Rainer Kallenbach, Michael Hahn > > ________________________________________ > From: Ganesh Murthy <gmur...@redhat.com> > Sent: Friday, July 14, 2017 15:14 > To: users@qpid.apache.org > Subject: Re: Dispatch Router throughput > > On Fri, Jul 14, 2017 at 8:43 AM, Gordon Sim <g...@redhat.com> wrote: > > > On 14/07/17 13:27, Hudalla Kai (INST/ECS4) wrote: > > > >> Not yet, but I can certainly turn it on. > >> > > > > No! I was checking it was off as the full logging can slow things down a > > lot (especially logging to a terminal). > > > > Is your test client available somewhere? I'm a bit puzzled as to what is > > going on and perhaps if I run it we can at least figure out whether its > the > > client or the router env that is causing the issue. > > Along with the test client, can you also please send your router config > file? Thanks. > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > > For additional commands, e-mail: users-h...@qpid.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
