You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Ted Ross <tr...@redhat.com> on 2014/02/24 20:03:22 UTC
Qpid Dispatch 0.2 beta-1
A number of important features and fixes have gone into Dispatch Router
since the initial release. I have created a beta release for Dispatch
0.2 for folks to test. The binary distribution can be found here:
http://people.apache.org/~tross/qpid-dispatch-0.2beta1/
The following improvements are included in 0.2beta1:
DISPATCH-1 Use Target Address from the link if there is no To field
in a message from a producer
DISPATCH-15 Add different forwarding semantics for addresses
DISPATCH-20 Implement the discovery operations in the [management] agent
DISPATCH-22 Reduce the time to detect loss of neighbor
DISPATCH-24 Add ssl option to system_tests_two_routers.py test
DISPATCH-28 Increase the length of the random portion of temporary
addresses.
The following bugs are fixed:
DISPATCH-17 Build system ignores user-defined CFLAGS
DISPATCH-18 SSL inter-router connections seem to run in-the-clear
DISPATCH-27 Intermittent test failures on RHEL platforms
DISPATCH-29 Spurious Mobile Address Requests (MAR) when connecting
to a remote router
DISPATCH-30 Wrong test configuration files installed
-Ted
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Qpid Dispatch 0.2 beta-1
Posted by "Darryl L. Pierce" <dp...@redhat.com>.
On Mon, Feb 24, 2014 at 02:03:22PM -0500, Ted Ross wrote:
> A number of important features and fixes have gone into Dispatch
> Router since the initial release. I have created a beta release for
> Dispatch 0.2 for folks to test. The binary distribution can be
> found here:
>
> http://people.apache.org/~tross/qpid-dispatch-0.2beta1/
>
> The following improvements are included in 0.2beta1:
>
> DISPATCH-1 Use Target Address from the link if there is no To
> field in a message from a producer
> DISPATCH-15 Add different forwarding semantics for addresses
> DISPATCH-20 Implement the discovery operations in the [management] agent
> DISPATCH-22 Reduce the time to detect loss of neighbor
> DISPATCH-24 Add ssl option to system_tests_two_routers.py test
> DISPATCH-28 Increase the length of the random portion of
> temporary addresses.
>
> The following bugs are fixed:
>
> DISPATCH-17 Build system ignores user-defined CFLAGS
> DISPATCH-18 SSL inter-router connections seem to run in-the-clear
> DISPATCH-27 Intermittent test failures on RHEL platforms
> DISPATCH-29 Spurious Mobile Address Requests (MAR) when
> connecting to a remote router
> DISPATCH-30 Wrong test configuration files installed
Initial packaging tests work well on Fedora 20.
--
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
Re: Qpid Dispatch 0.2 beta-1
Posted by Gordon Sim <gs...@redhat.com>.
On 02/24/2014 07:03 PM, Ted Ross wrote:
> A number of important features and fixes have gone into Dispatch Router
> since the initial release. I have created a beta release for Dispatch
> 0.2 for folks to test. The binary distribution can be found here:
>
> http://people.apache.org/~tross/qpid-dispatch-0.2beta1/
I've built and tested this and it looks good to me. The addition of the
routing semantics (allowing addresses to be configured for competing and
non-competing consumers) is very useful and I would be in favour of
proceeding to release this.
> The following improvements are included in 0.2beta1:
>
> DISPATCH-1 Use Target Address from the link if there is no To field
> in a message from a producer
> DISPATCH-15 Add different forwarding semantics for addresses
> DISPATCH-20 Implement the discovery operations in the [management]
> agent
> DISPATCH-22 Reduce the time to detect loss of neighbor
> DISPATCH-24 Add ssl option to system_tests_two_routers.py test
> DISPATCH-28 Increase the length of the random portion of temporary
> addresses.
>
> The following bugs are fixed:
>
> DISPATCH-17 Build system ignores user-defined CFLAGS
> DISPATCH-18 SSL inter-router connections seem to run in-the-clear
> DISPATCH-27 Intermittent test failures on RHEL platforms
> DISPATCH-29 Spurious Mobile Address Requests (MAR) when connecting
> to a remote router
> DISPATCH-30 Wrong test configuration files installed
>
> -Ted
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [VOTE] Dispatch Router release 0.2
Posted by Gordon Sim <gs...@redhat.com>.
+1 for releasing this. It has useful additions to 0.1 and getting it out
to those interested is valuable.
On 04/04/2014 08:24 PM, Ted Ross wrote:
> The 0.2beta1 cut of Dispatch Router has been out for over a month and
> has been tested by several people with no issues discovered. I'm
> starting a vote on using this tarball for the 0.2 release. The Jira
> list is below, but the most important feature for this release is
> DISPATCH-15 which adds configurable forwarding semantics (fanout vs.
> single consumer).
>
> Thanks,
>
> -Ted
>
>
> -------- Original Message --------
> Subject: Qpid Dispatch 0.2 beta-1
> Date: Mon, 24 Feb 2014 14:03:22 -0500
> From: Ted Ross <tr...@redhat.com>
> Reply-To: users@qpid.apache.org
> To: users@qpid.apache.org <us...@qpid.apache.org>
>
>
>
> A number of important features and fixes have gone into Dispatch Router
> since the initial release. I have created a beta release for Dispatch
> 0.2 for folks to test. The binary distribution can be found here:
>
> http://people.apache.org/~tross/qpid-dispatch-0.2beta1/
>
> The following improvements are included in 0.2beta1:
>
> DISPATCH-1 Use Target Address from the link if there is no To field
> in a message from a producer
> DISPATCH-15 Add different forwarding semantics for addresses
> DISPATCH-20 Implement the discovery operations in the [management]
> agent
> DISPATCH-22 Reduce the time to detect loss of neighbor
> DISPATCH-24 Add ssl option to system_tests_two_routers.py test
> DISPATCH-28 Increase the length of the random portion of temporary
> addresses.
>
> The following bugs are fixed:
>
> DISPATCH-17 Build system ignores user-defined CFLAGS
> DISPATCH-18 SSL inter-router connections seem to run in-the-clear
> DISPATCH-27 Intermittent test failures on RHEL platforms
> DISPATCH-29 Spurious Mobile Address Requests (MAR) when connecting
> to a remote router
> DISPATCH-30 Wrong test configuration files installed
>
> -Ted
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [VOTE RESULT] Dispatch Router release 0.2
Posted by Ted Ross <tr...@redhat.com>.
This vote has passed with four +1 votes (3 binding) and no -1s. I will
tag and release shortly.
Thanks,
-Ted
On 04/04/2014 03:24 PM, Ted Ross wrote:
> The 0.2beta1 cut of Dispatch Router has been out for over a month and
> has been tested by several people with no issues discovered. I'm
> starting a vote on using this tarball for the 0.2 release. The Jira
> list is below, but the most important feature for this release is
> DISPATCH-15 which adds configurable forwarding semantics (fanout vs.
> single consumer).
>
> Thanks,
>
> -Ted
>
>
> -------- Original Message --------
> Subject: Qpid Dispatch 0.2 beta-1
> Date: Mon, 24 Feb 2014 14:03:22 -0500
> From: Ted Ross <tr...@redhat.com>
> Reply-To: users@qpid.apache.org
> To: users@qpid.apache.org <us...@qpid.apache.org>
>
>
>
> A number of important features and fixes have gone into Dispatch Router
> since the initial release. I have created a beta release for Dispatch
> 0.2 for folks to test. The binary distribution can be found here:
>
> http://people.apache.org/~tross/qpid-dispatch-0.2beta1/
>
> The following improvements are included in 0.2beta1:
>
> DISPATCH-1 Use Target Address from the link if there is no To field
> in a message from a producer
> DISPATCH-15 Add different forwarding semantics for addresses
> DISPATCH-20 Implement the discovery operations in the [management]
> agent
> DISPATCH-22 Reduce the time to detect loss of neighbor
> DISPATCH-24 Add ssl option to system_tests_two_routers.py test
> DISPATCH-28 Increase the length of the random portion of temporary
> addresses.
>
> The following bugs are fixed:
>
> DISPATCH-17 Build system ignores user-defined CFLAGS
> DISPATCH-18 SSL inter-router connections seem to run in-the-clear
> DISPATCH-27 Intermittent test failures on RHEL platforms
> DISPATCH-29 Spurious Mobile Address Requests (MAR) when connecting
> to a remote router
> DISPATCH-30 Wrong test configuration files installed
>
> -Ted
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: dispatch router perf tests (was Re: [VOTE] Dispatch Router release
0.2)
Posted by Ted Ross <tr...@redhat.com>.
On 04/10/2014 06:26 AM, Gordon Sim wrote:
> On 04/10/2014 10:53 AM, Michael Goulish wrote:
>> Also did 40 million-message load-test
>> 3 separate boxes:
>> * 1 box for 40 senders
>> * 1 box for 2-router network
>> * 1 box for 40 receivers.
>> * messages are 117 bytes each
>>
>> results:
>>
>> * 182,000 messages per second, round-trip, i.e. 364,000 transfers
>> per second.
>> * memory on routers not growing
>> * the 2 routers used 34% of total available CPU on a 16-core box.
>> * throughput on each ethernet interface was 21 MB/sec
This is a promising early result. There are two major areas for
performance tuning that I have in mind. The first is converting
Dispatch to use the new event API in Proton Engine. This should reduce
CPU utilization per transfer by eliminating an oft-repeated linear
search through all the available links. The second is improving the
lock architecture around the routing data structures. Currently there is
a single router lock which has too-large of a scope. Fixing this should
increase the utilization of available CPU.
>
> This is interesting... what did you use for these tests? Existing
> checked in clients or some custom benchmarking tool?
>
> Were the senders and receivers paired? I.e. did each sender send to
> one specific receiver? Or did each sender broadcast to all receivers?
> How did you measure the throughput?
>
> One of the key experiments I would like to see is a measurement of how
> overall throughput can scale out when adding extra routers. So e.g.
> for a broadcast pattern, with publishers publishing at some fixed
> rate, see how many publishers and receivers can be supported at that
> rate by one router, then add in a second router and see how many more
> publishers and receivers the combined network can then handle. (A
> similar test could be done for unicast).
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: dispatch router perf tests (was Re: [VOTE] Dispatch Router
release 0.2)
Posted by Michael Goulish <mg...@redhat.com>.
----- Original Message -----
> On 04/10/2014 10:53 AM, Michael Goulish wrote:
> > Also did 40 million-message load-test
> > 3 separate boxes:
> > * 1 box for 40 senders
> > * 1 box for 2-router network
> > * 1 box for 40 receivers.
> > * messages are 117 bytes each
> >
> > results:
> >
> > * 182,000 messages per second, round-trip, i.e. 364,000 transfers per
> > second.
> > * memory on routers not growing
> > * the 2 routers used 34% of total available CPU on a 16-core box.
> > * throughput on each ethernet interface was 21 MB/sec
>
> This is interesting... what did you use for these tests? Existing
> checked in clients or some custom benchmarking tool?
I used a sender and a receiver client that I wrote in C++.
>
> Were the senders and receivers paired? I.e. did each sender send to one
> specific receiver? Or did each sender broadcast to all receivers? How
> did you measure the throughput?
Well, I *thought* that they were paired, but in fact he senders
were broadcasting such that each sender's message went to 1 receiver on
each router.
>
> One of the key experiments I would like to see is a measurement of how
> overall throughput can scale out when adding extra routers. So e.g. for
> a broadcast pattern, with publishers publishing at some fixed rate, see
> how many publishers and receivers can be supported at that rate by one
> router, then add in a second router and see how many more publishers and
> receivers the combined network can then handle. (A similar test could be
> done for unicast).
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
dispatch router perf tests (was Re: [VOTE] Dispatch Router release
0.2)
Posted by Gordon Sim <gs...@redhat.com>.
On 04/10/2014 10:53 AM, Michael Goulish wrote:
> Also did 40 million-message load-test
> 3 separate boxes:
> * 1 box for 40 senders
> * 1 box for 2-router network
> * 1 box for 40 receivers.
> * messages are 117 bytes each
>
> results:
>
> * 182,000 messages per second, round-trip, i.e. 364,000 transfers per second.
> * memory on routers not growing
> * the 2 routers used 34% of total available CPU on a 16-core box.
> * throughput on each ethernet interface was 21 MB/sec
This is interesting... what did you use for these tests? Existing
checked in clients or some custom benchmarking tool?
Were the senders and receivers paired? I.e. did each sender send to one
specific receiver? Or did each sender broadcast to all receivers? How
did you measure the throughput?
One of the key experiments I would like to see is a measurement of how
overall throughput can scale out when adding extra routers. So e.g. for
a broadcast pattern, with publishers publishing at some fixed rate, see
how many publishers and receivers can be supported at that rate by one
router, then add in a second router and see how many more publishers and
receivers the combined network can then handle. (A similar test could be
done for unicast).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [VOTE] Dispatch Router release 0.2
Posted by Michael Goulish <mg...@redhat.com>.
(sorry, am I late? I was abducted. Missing time experience. )
my vote:
Nihil Obstat -- Imprimatur
( +1 )
I tested startup of 2-router network, 100 times with no problem
Also did 40 million-message load-test
3 separate boxes:
* 1 box for 40 senders
* 1 box for 2-router network
* 1 box for 40 receivers.
* messages are 117 bytes each
results:
* 182,000 messages per second, round-trip, i.e. 364,000 transfers per second.
* memory on routers not growing
* the 2 routers used 34% of total available CPU on a 16-core box.
* throughput on each ethernet interface was 21 MB/sec
----- Original Message -----
The 0.2beta1 cut of Dispatch Router has been out for over a month and
has been tested by several people with no issues discovered. I'm
starting a vote on using this tarball for the 0.2 release. The Jira
list is below, but the most important feature for this release is
DISPATCH-15 which adds configurable forwarding semantics (fanout vs.
single consumer).
Thanks,
-Ted
-------- Original Message --------
Subject: Qpid Dispatch 0.2 beta-1
Date: Mon, 24 Feb 2014 14:03:22 -0500
From: Ted Ross <tr...@redhat.com>
Reply-To: users@qpid.apache.org
To: users@qpid.apache.org <us...@qpid.apache.org>
A number of important features and fixes have gone into Dispatch Router
since the initial release. I have created a beta release for Dispatch
0.2 for folks to test. The binary distribution can be found here:
http://people.apache.org/~tross/qpid-dispatch-0.2beta1/
The following improvements are included in 0.2beta1:
DISPATCH-1 Use Target Address from the link if there is no To field
in a message from a producer
DISPATCH-15 Add different forwarding semantics for addresses
DISPATCH-20 Implement the discovery operations in the [management] agent
DISPATCH-22 Reduce the time to detect loss of neighbor
DISPATCH-24 Add ssl option to system_tests_two_routers.py test
DISPATCH-28 Increase the length of the random portion of temporary
addresses.
The following bugs are fixed:
DISPATCH-17 Build system ignores user-defined CFLAGS
DISPATCH-18 SSL inter-router connections seem to run in-the-clear
DISPATCH-27 Intermittent test failures on RHEL platforms
DISPATCH-29 Spurious Mobile Address Requests (MAR) when connecting
to a remote router
DISPATCH-30 Wrong test configuration files installed
-Ted
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [VOTE] Dispatch Router release 0.2
Posted by Ted Ross <tr...@redhat.com>.
Please note that there was an issue found with DISPATCH-1. It has been
re-opened and deferred to 0.3.
On 04/04/2014 03:24 PM, Ted Ross wrote:
> The 0.2beta1 cut of Dispatch Router has been out for over a month and
> has been tested by several people with no issues discovered. I'm
> starting a vote on using this tarball for the 0.2 release. The Jira
> list is below, but the most important feature for this release is
> DISPATCH-15 which adds configurable forwarding semantics (fanout vs.
> single consumer).
>
> Thanks,
>
> -Ted
>
>
> -------- Original Message --------
> Subject: Qpid Dispatch 0.2 beta-1
> Date: Mon, 24 Feb 2014 14:03:22 -0500
> From: Ted Ross <tr...@redhat.com>
> Reply-To: users@qpid.apache.org
> To: users@qpid.apache.org <us...@qpid.apache.org>
>
>
>
> A number of important features and fixes have gone into Dispatch Router
> since the initial release. I have created a beta release for Dispatch
> 0.2 for folks to test. The binary distribution can be found here:
>
> http://people.apache.org/~tross/qpid-dispatch-0.2beta1/
>
> The following improvements are included in 0.2beta1:
>
> DISPATCH-1 Use Target Address from the link if there is no To field
> in a message from a producer
> DISPATCH-15 Add different forwarding semantics for addresses
> DISPATCH-20 Implement the discovery operations in the [management]
> agent
> DISPATCH-22 Reduce the time to detect loss of neighbor
> DISPATCH-24 Add ssl option to system_tests_two_routers.py test
> DISPATCH-28 Increase the length of the random portion of temporary
> addresses.
>
> The following bugs are fixed:
>
> DISPATCH-17 Build system ignores user-defined CFLAGS
> DISPATCH-18 SSL inter-router connections seem to run in-the-clear
> DISPATCH-27 Intermittent test failures on RHEL platforms
> DISPATCH-29 Spurious Mobile Address Requests (MAR) when connecting
> to a remote router
> DISPATCH-30 Wrong test configuration files installed
>
> -Ted
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [VOTE] Dispatch Router release 0.2
Posted by "aconway.rh" <ac...@redhat.com>.
+1 to release this, basic testing shows no problems.
Ted Ross wrote
> The 0.2beta1 cut of Dispatch Router has been out for over a month and
> has been tested by several people with no issues discovered. I'm
> starting a vote on using this tarball for the 0.2 release. The Jira
> list is below, but the most important feature for this release is
> DISPATCH-15 which adds configurable forwarding semantics (fanout vs.
> single consumer).
>
> Thanks,
>
> -Ted
>
>
> -------- Original Message --------
> Subject: Qpid Dispatch 0.2 beta-1
> Date: Mon, 24 Feb 2014 14:03:22 -0500
> From: Ted Ross <
> tross@
> >
> Reply-To:
> users@.apache
> To:
> users@.apache
> <
> users@.apache
> >
>
>
>
> A number of important features and fixes have gone into Dispatch Router
> since the initial release. I have created a beta release for Dispatch
> 0.2 for folks to test. The binary distribution can be found here:
>
> http://people.apache.org/~tross/qpid-dispatch-0.2beta1/
>
> The following improvements are included in 0.2beta1:
>
> DISPATCH-1 Use Target Address from the link if there is no To field
> in a message from a producer
> DISPATCH-15 Add different forwarding semantics for addresses
> DISPATCH-20 Implement the discovery operations in the [management]
> agent
> DISPATCH-22 Reduce the time to detect loss of neighbor
> DISPATCH-24 Add ssl option to system_tests_two_routers.py test
> DISPATCH-28 Increase the length of the random portion of temporary
> addresses.
>
> The following bugs are fixed:
>
> DISPATCH-17 Build system ignores user-defined CFLAGS
> DISPATCH-18 SSL inter-router connections seem to run in-the-clear
> DISPATCH-27 Intermittent test failures on RHEL platforms
> DISPATCH-29 Spurious Mobile Address Requests (MAR) when connecting
> to a remote router
> DISPATCH-30 Wrong test configuration files installed
>
> -Ted
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> users-unsubscribe@.apache
> For additional commands, e-mail:
> users-help@.apache
--
View this message in context: http://qpid.2158936.n2.nabble.com/Qpid-Dispatch-0-2-beta-1-tp7604788p7606914.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
[VOTE] Dispatch Router release 0.2
Posted by Ted Ross <tr...@redhat.com>.
The 0.2beta1 cut of Dispatch Router has been out for over a month and
has been tested by several people with no issues discovered. I'm
starting a vote on using this tarball for the 0.2 release. The Jira
list is below, but the most important feature for this release is
DISPATCH-15 which adds configurable forwarding semantics (fanout vs.
single consumer).
Thanks,
-Ted
-------- Original Message --------
Subject: Qpid Dispatch 0.2 beta-1
Date: Mon, 24 Feb 2014 14:03:22 -0500
From: Ted Ross <tr...@redhat.com>
Reply-To: users@qpid.apache.org
To: users@qpid.apache.org <us...@qpid.apache.org>
A number of important features and fixes have gone into Dispatch Router
since the initial release. I have created a beta release for Dispatch
0.2 for folks to test. The binary distribution can be found here:
http://people.apache.org/~tross/qpid-dispatch-0.2beta1/
The following improvements are included in 0.2beta1:
DISPATCH-1 Use Target Address from the link if there is no To field
in a message from a producer
DISPATCH-15 Add different forwarding semantics for addresses
DISPATCH-20 Implement the discovery operations in the [management] agent
DISPATCH-22 Reduce the time to detect loss of neighbor
DISPATCH-24 Add ssl option to system_tests_two_routers.py test
DISPATCH-28 Increase the length of the random portion of temporary
addresses.
The following bugs are fixed:
DISPATCH-17 Build system ignores user-defined CFLAGS
DISPATCH-18 SSL inter-router connections seem to run in-the-clear
DISPATCH-27 Intermittent test failures on RHEL platforms
DISPATCH-29 Spurious Mobile Address Requests (MAR) when connecting
to a remote router
DISPATCH-30 Wrong test configuration files installed
-Ted
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org