Serge Knystautas wrote: > > > On 5/31/07, robert burrell donkin > <[EMAIL PROTECTED]> wrote: > > On 5/31/07, Bernd Fondermann > <[EMAIL PROTECTED]> wrote: > > > On a different note, some user back then noted that it could be > > > worthwhile to use JMeter as a test container infrastructure. > > > > a postage plugin for jmeter might be interesting > > Have you guys ever been able to use JMeter for load testing? I've had > limited success as a functional test suite, but when I tried to use it > for load testing, the client consumed vastly more resources than the > server... maybe I was using an old version. > > I'm just a bit concerned that JMeter couldn't generate the load that > Postage could. Hopefully someone has experience that can refute this.
Like similar tools, JMeter consumes a fair bit of horsepower running the tests. This is why the user manual says... "Note that while you can indeed execute the JMeterEngine on your application server, you need to be mindful of the fact that this will be adding processing overhead on the application server and thus your testing results will be somewhat tainted. The recommended approach is to have one or more machines on the same Ethernet segment as your application server that you configure to run the JMeter Engine. This will minimize the impact of the network on the test results without impacting the performance of the application serer itself". When load testing I establish a standalone gigabyte network of sufficient client machines to deliver the required load to the server under test without themselves having bottlenecks. Cheers -- Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
