On 12/11/2007, Sonam Chauhan <[EMAIL PROTECTED]> wrote: > Sebb: > > > It's mainly a problem because of the data volumes that are required. I > > don't see how changing the transport mechanism can change that. > > I thought Spread had bandwidth throttling features so that logs entries > could queue up and stream in a bandwidth limited manner to the end > destination - however Spread may not have these features. A workaround
Ah - I see. That might help, but it would prolong the end of a test, as the queued entries must be allowed to filter through. There's also the question of where the queued entries are stored. > would be to setup virtual network interfaces limited to, say, 10 Mbps > and have the Spread components bind to those interfaces, but that may be > too much work. It may also be a lot of work to incorporate the Spread protocol into JMeter. > In any case, I've asked the question on the Spread user > list. Thanks. > > > Is it possible to prototype this idea using a BeanShell listener? > > > > > > I think it would be difficult. > > > > Listeners are handled specially in client-server mode. > > Thanks. > > Kind regards, > Sonam Chauhan > -- > Corporate Express Australia Ltd. > Phone: +61-2-93350725, Email: [EMAIL PROTECTED] > > -----Original Message----- > From: sebb [mailto:[EMAIL PROTECTED] > Sent: Friday, 9 November 2007 12:57 AM > To: JMeter Users List > Subject: Re: 'Spread' for distributed testing > > In 08/11/2007, Sonam Chauhan <[EMAIL PROTECTED]> wrote: > > Just a thought - Would the 'Spread Toolkit' (http://www.spread.org/) > be > > useful in JMeter distributed testing? > > > > > > > > From the Spread website: > > > > Spread functions as a unified message bus for distributed > applications, > > and provides highly tuned application-level multicast, group > > communication, and point to point support. > > > > > > > > From what I understand, an existing problem in JMeter distributed > > testing is collating logs back to the master server, particularly when > > the logs capture extra information (e.g., the HTTP response). Perhaps > > using Spread could help in this? It has a Java API encapsulated in one > > package. > > > > It's mainly a problem because of the data volumes that are required. I > don't see how changing the transport mechanism can change that. > > > > > Is it possible to prototype this idea using a BeanShell listener? > > > > I think it would be difficult. > > Listeners are handled specially in client-server mode. > > > > > Kind regards, > > Thanks anyway. > > > Sonam Chauhan > > > > -- > > > > Corporate Express Australia Ltd. > > > > Phone: +61-2-93350725, Email: [EMAIL PROTECTED] > > > > > > > > Spread Toolkit > > > > http://www.spread.org/ > > > > > > > > Java Interface to the Spread Toolkit > > > > http://www.spread.org/docs/javadocs/java.html > > > > > > > > An interesting article on using Spread to unify apache access logs. > > > > http://www.samag.com/documents/s=7789/sam0302a/0302a.htm > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
