Mailing-List: contact qpid-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: qpid-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of rupertlssmith@googlemail.com
 designates 64.233.162.225 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=igBMkhq1mSZ8t0hVnEl8iw/IBQ4G4G8Xqkqe7Q+yOGQl4oyc00Juk8bfduRM96IfXTOXCsDdAZzwG2zSEnsHSTDh/VIT/8NR+IG49ozZF5q25x9HonFOxMbWyTPMYAraap9OI1Dn7qdWUyfo2xeRM6T+gms4/EhUCIbUK8WeKVM=
Message-ID: <a21e8c210705020838o79ba1688w9be3ddfc4aa37410@mail.gmail.com>
Date: Wed, 2 May 2007 16:38:41 +0100
From: "Rupert Smith" <rupertlssmith@googlemail.com>
To: qpid-dev@incubator.apache.org
Subject: Re: C++ M2 JIRAs
In-Reply-To: <46388372.7060300@redhat.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_10824_16248894.1178120321787"
References: <1177356048.32369.20.camel@localhost.localdomain>
	 <4635AF72.3040409@redhat.com>
	 <a21e8c210705020229i69d79223gcc4a4d70fa81128c@mail.gmail.com>
	 <46386171.4090306@redhat.com>
	 <a21e8c210705020340q1ab02532m570d0b1ffa1dfffe@mail.gmail.com>
	 <4638734D.9020404@redhat.com>
	 <a21e8c210705020429n1a1c5f77j956ca841f712a0b2@mail.gmail.com>
	 <46388372.7060300@redhat.com>

------=_Part_10824_16248894.1178120321787
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Your point about trying to make the coordinator not care too much about the
what the clients are doing is valid, and worth pursuing for the purpose of
making the coordinator abstract enough to be re-usable for different kinds
of tests. I think the coordinator as a whole does need to be aware of the
roles it assigns to test clients to ensure that it assigns receiver roles
before starting senders. This behaviour has been encapsulated in the
CoordinatingTestCase class.

The purpose of CoordinatingTestCase is to coordinate a two participant
sender/receiver test. I may pull an interface out of it add another
implementation the purpose of which is to coordinate a multi-client
performance test. This will consist of a group of 'senders' (which probably
also consume their own messages), spread over a set of test machines, and
the coordinator will be used to to run a distributed test using the test
machines to try and provide a better simulation of broker load with a large
number of connections. One limit of the current performance tests is that
they only run on a single client machine, limiting their scalability.
Performance tests have been run up to 1000 connections, but with that many
threads on the client machine, the overhead impacts the results obtained.

Should be able to do distributed performance testing with the current design
by only changing the coordinator to introduce a new kind of test case,
without making any changes to existing interop test clients.

On 02/05/07, Gordon Sim <gsim@redhat.com> wrote:
>
> Rupert Smith wrote:
> > Ok, lets just leave things as they are then. Seems more important to
> just
> > get the code written at the moment. I'll add those clarifications.
>
> Well, if we want to make the changes at some point, now would be the
> best time before more code is in place. The question is whether they
> actually simplify things or whether they just represent my preference.
> However, I can live with whats there now.
>

------=_Part_10824_16248894.1178120321787--