--- Paul Fremantle <[EMAIL PROTECTED]> wrote: > I've tried JMeter in the past, but its not very fast > itself, so > typically it requires a much bigger machine that the > server, or a > network of clients to work effectively. We'll take a > look at the > benchmark clients you posted though.
I'm glad I'm not the only one with such experiences. Service I tried to test has peak rate of above 2k per second, and testable using simple load testing client (on top of HttpClient, or even Sun's default http connection). But via JMeter I could never get over about 250 per second, on a reasonably new desktop. But what I was wondering was what exactly causes such overhead... ie. is it due to design (really meant for low-to-medium request rates), implementation problems, or just overhead from visualization components. Has anyone had better luck in getting higher throughput rates from JMeter? Any specific tuning, settings that might help? I know that this is more a JMeter question, but given that this seems to affect generic XML-over-HTTP requests, which usually use HttpClient, I hope it's somewhat relevant question -+ Tatu +- ____________________________________________________________________________________ Bored stiff? Loosen up... Download and play hundreds of games for free on Yahoo! Games. http://games.yahoo.com/games/front --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
