Re: Dispatch Router throughput
Hi Chuck,
thanks for the advice. Sadly, though, this doesn't seem to have any (positive)
impact, i.e. using the config below, we still only get max 2500 msg/sec
throughput.
[
["router", {
"id": "Hono.Example.Router",
"mode": "standalone",
"workerThreads": 4
}],
["listener", {
"host": "0.0.0.0",
"port": 5672,
"authenticatePeer": "no",
"linkCapacity": 1000
}],
["address", {
"prefix": "telemetry/",
"distribution": "balanced"
}],
["policy", {
"maxConnections": 1000,
"enableVhostPolicy": true
}],
["vhost", {
"id": "$default",
"maxConnections": 100,
"allowUnknownUser": true,
"groups": {
"$default": {
"remoteHosts": "*",
"maxSessions": 500,
"maxMessageSize": 204800,
"allowUserIdProxy": true,
"sources": "*",
"targets": "*"
}
}
}],
["log", {
"module": "DEFAULT",
"enable": "info+"
}]
]
Any thoughts?
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: Chuck Rolke
Sent: Tuesday, July 18, 2017 20:40
To: users@qpid.apache.org
Subject: Re: Dispatch Router throughput
In the hono vhost policy section try adding:
"allowUserIdProxy": true
If the user id proxy setting is false then the router must parse every
message through to the user-id field of the message properties. Then
verify that the user has no name in the message user-id or the
same name that was used when the connection was created.
Allowing the user id proxy bypasses the per-message parsing and checking.
The down side of setting the user id proxy to true is it allows
the user to launch messages into the system with any user-id.
Per-message checks are avoided altogether when the messages arrive
over a 'link routed' path. That should give you even better numbers.
-Chuck
- Original Message -
> From: "Hudalla Kai (INST/ECS4)"
> To: users@qpid.apache.org
> Sent: Tuesday, July 18, 2017 11:21:40 AM
> Subject: Re: Dispatch Router throughput
>
> Hi,
>
> I think we have narrowed it down.
>
> Running the quiver test as suggested by Gordon (thanks for that :-)) and
> using the Dispatch Router config below, we get around 3 msg/sec if we
> set "enableVhostPolicy" to false and around 2500 msgs/sec when we set it to
> "true".
>
> [
> ["router", {
> "id": "Hono.Example.Router",
> "mode": "standalone",
> "workerThreads": 4
> }],
>
> ["listener", {
> "host": "0.0.0.0",
> "port": 5672,
> "authenticatePeer": false,
> "linkCapacity": 1000
> }],
>
> ["policy", {
> "enableVhostPolicy": false,
> "defaultVhost": "hono"
> }],
>
> ["vhost", {
> "id": "hono",
> "allowUnknownUser": true,
> "groups": {
> "$default": {
> "remoteHosts": "*",
> "sources": "*",
> "targets": "*"
> }
> }
> }],
>
> ["log", {
> "module": "DEFAULT",
> "enable": "info+"
> }]
> ]
>
> We are running the test against the enmasseproject/qdrouterd-base:0.8.0-1
> Docker image.
> Is this the expected behavior?
>
> 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: Gordon Sim
> Sent: Tuesday, July 18, 2017 14:05
> To: users@qpid.apache.org
> Subject: Re: Dispatch Router throughput
>
> On 18/07/17 11:53, Hudalla Kai (INST/ECS4) wrote:
> > 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?
>
> Using that image (default config) with qpid-send/qpid-receive from
> qpid::messaging, I see >90k msgs/sec, so I don't think it is the image.
>
> Using the vertx-proton option for Justin Ross's quiver benchmark[1]
> against that same image I get ~39k msgs/sec.
>
> [1] https://github.com/ssorj/quiver/
>
> -
> 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 addit
Re: Getting involved with Apache Qpid
Hi Ben, Thank you for introducing yourself and welcome to the Apache Qpid community! Documentation pro?! Awesome! Can I get you a cup of coffee? ;-) make yourself at home please. -Steve > On Jul 18, 2017, at 6:25 PM, Ben Hardesty wrote: > > Hi all, > > I'm starting to get involved in the Apache Qpid project, so I wanted to > take a quick moment to introduce myself. My primary interest is the > Dispatch Router, which I've been using/playing around with for about a year > now. I have a background in distributed systems, and my specialty is > documentation - I've been writing docs professionally as a tech writer for > about 15 years. > > To get started, I've contributed some small updates to the qdmanage, > qdstat, and qdrouterd man pages (typo fixes, editing for consistency and > clarity, etc.), and I'll have more to come for the Dispatch Router book and > qdrouterd.conf man page. > > In the mean time, if anyone has any doc-related questions or thoughts, > please feel free to reach out. I'm happy to help out as I can with editing, > advising, and writing. I hang out as bhardesty on the #qpid channel. > > Thanks, > Ben Hardesty - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Getting involved with Apache Qpid
Hi all, I'm starting to get involved in the Apache Qpid project, so I wanted to take a quick moment to introduce myself. My primary interest is the Dispatch Router, which I've been using/playing around with for about a year now. I have a background in distributed systems, and my specialty is documentation - I've been writing docs professionally as a tech writer for about 15 years. To get started, I've contributed some small updates to the qdmanage, qdstat, and qdrouterd man pages (typo fixes, editing for consistency and clarity, etc.), and I'll have more to come for the Dispatch Router book and qdrouterd.conf man page. In the mean time, if anyone has any doc-related questions or thoughts, please feel free to reach out. I'm happy to help out as I can with editing, advising, and writing. I hang out as bhardesty on the #qpid channel. Thanks, Ben Hardesty
Re: Dispatch Router throughput
In the hono vhost policy section try adding:
"allowUserIdProxy": true
If the user id proxy setting is false then the router must parse every
message through to the user-id field of the message properties. Then
verify that the user has no name in the message user-id or the
same name that was used when the connection was created.
Allowing the user id proxy bypasses the per-message parsing and checking.
The down side of setting the user id proxy to true is it allows
the user to launch messages into the system with any user-id.
Per-message checks are avoided altogether when the messages arrive
over a 'link routed' path. That should give you even better numbers.
-Chuck
- Original Message -
> From: "Hudalla Kai (INST/ECS4)"
> To: users@qpid.apache.org
> Sent: Tuesday, July 18, 2017 11:21:40 AM
> Subject: Re: Dispatch Router throughput
>
> Hi,
>
> I think we have narrowed it down.
>
> Running the quiver test as suggested by Gordon (thanks for that :-)) and
> using the Dispatch Router config below, we get around 3 msg/sec if we
> set "enableVhostPolicy" to false and around 2500 msgs/sec when we set it to
> "true".
>
> [
> ["router", {
> "id": "Hono.Example.Router",
> "mode": "standalone",
> "workerThreads": 4
> }],
>
> ["listener", {
> "host": "0.0.0.0",
> "port": 5672,
> "authenticatePeer": false,
> "linkCapacity": 1000
> }],
>
> ["policy", {
> "enableVhostPolicy": false,
> "defaultVhost": "hono"
> }],
>
> ["vhost", {
> "id": "hono",
> "allowUnknownUser": true,
> "groups": {
> "$default": {
> "remoteHosts": "*",
> "sources": "*",
> "targets": "*"
> }
> }
> }],
>
> ["log", {
> "module": "DEFAULT",
> "enable": "info+"
> }]
> ]
>
> We are running the test against the enmasseproject/qdrouterd-base:0.8.0-1
> Docker image.
> Is this the expected behavior?
>
> 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: Gordon Sim
> Sent: Tuesday, July 18, 2017 14:05
> To: users@qpid.apache.org
> Subject: Re: Dispatch Router throughput
>
> On 18/07/17 11:53, Hudalla Kai (INST/ECS4) wrote:
> > 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?
>
> Using that image (default config) with qpid-send/qpid-receive from
> qpid::messaging, I see >90k msgs/sec, so I don't think it is the image.
>
> Using the vertx-proton option for Justin Ross's quiver benchmark[1]
> against that same image I get ~39k msgs/sec.
>
> [1] https://github.com/ssorj/quiver/
>
> -
> 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
Re: Dispatch Router throughput
Hi,
I think we have narrowed it down.
Running the quiver test as suggested by Gordon (thanks for that :-)) and using
the Dispatch Router config below, we get around 3 msg/sec if we set
"enableVhostPolicy" to false and around 2500 msgs/sec when we set it to "true".
[
["router", {
"id": "Hono.Example.Router",
"mode": "standalone",
"workerThreads": 4
}],
["listener", {
"host": "0.0.0.0",
"port": 5672,
"authenticatePeer": false,
"linkCapacity": 1000
}],
["policy", {
"enableVhostPolicy": false,
"defaultVhost": "hono"
}],
["vhost", {
"id": "hono",
"allowUnknownUser": true,
"groups": {
"$default": {
"remoteHosts": "*",
"sources": "*",
"targets": "*"
}
}
}],
["log", {
"module": "DEFAULT",
"enable": "info+"
}]
]
We are running the test against the enmasseproject/qdrouterd-base:0.8.0-1
Docker image.
Is this the expected behavior?
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: Gordon Sim
Sent: Tuesday, July 18, 2017 14:05
To: users@qpid.apache.org
Subject: Re: Dispatch Router throughput
On 18/07/17 11:53, Hudalla Kai (INST/ECS4) wrote:
> 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?
Using that image (default config) with qpid-send/qpid-receive from
qpid::messaging, I see >90k msgs/sec, so I don't think it is the image.
Using the vertx-proton option for Justin Ross's quiver benchmark[1]
against that same image I get ~39k msgs/sec.
[1] https://github.com/ssorj/quiver/
-
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
Re: Dispatch Router throughput
On 18/07/17 11:53, Hudalla Kai (INST/ECS4) wrote: 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? Using that image (default config) with qpid-send/qpid-receive from qpid::messaging, I see >90k msgs/sec, so I don't think it is the image. Using the vertx-proton option for Justin Ross's quiver benchmark[1] against that same image I get ~39k msgs/sec. [1] https://github.com/ssorj/quiver/ - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: Dispatch Router throughput
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 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 > 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 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
