The Artima Developer Community
Sponsored Link

Agile Buzz Forum
Web Velocity Load Testing

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
James Robertson

Posts: 29924
Nickname: jarober61
Registered: Jun, 2003

David Buck, Smalltalker at large
Web Velocity Load Testing Posted: Nov 21, 2008 11:54 AM
Reply to this message Reply

This post originated from an RSS feed registered with Agile Buzz by James Robertson.
Original Post: Web Velocity Load Testing
Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants
Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml
Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general.
Latest Agile Buzz Posts
Latest Agile Buzz Posts by James Robertson
Latest Posts From Cincom Smalltalk Blog - Smalltalk with Rants

Advertisement

Using httperf, I decided to run a few load tests against a simple "Hello World" type app - in the latest Web Velocity build I have installed. Now, based on my previous uses of httperf, I have limitations on the number of open sockets I can use at once - it seems to tap out around 40 requests/second on the client (i.e., the Mac I'm using to run httperf). Web Velocity didn't seem to even notice the load at that level, so if anyone has better tools to recommend, I'd love to hear about them. Anyway - I used this command against the app

httperf --verbose --hog --timeout=10 --client=0/1 --server=mickey.local --port=7777
--uri=/HelloWorld/Hello --rate=40 --send-buffer=4096 --recv-buffer=16384 --num-conns=1000
--num-calls=1


httperf: maximum number of open descriptors = 1024
reply-rate = 40.0    
reply-rate = 40.0    
reply-rate = 40.0    
reply-rate = 40.0    
reply-rate = 39.8    
Maximum connect burst length: 1

Total: connections 1000 requests 1000 replies 1000 test-duration 25.000 s

Connection rate: 40.0 conn/s (25.0 ms/conn, <=2 concurrent connections)
Connection time [ms]: min 3.3 avg 7.8 max 36.0 median 6.5 stddev 3.7
Connection time [ms]: connect 0.6
Connection length [replies/conn]: 1.000

Request rate: 40.0 req/s (25.0 ms/req)
Request size [B]: 81.0

Reply rate [replies/s]: min 39.8 avg 40.0 max 40.0 stddev 0.1 (5 samples)
Reply time [ms]: response 7.2 transfer 0.0
Reply size [B]: header 181.0 content 1782.0 footer 0.0 (total 1963.0)
Reply status: 1xx=0 2xx=1000 3xx=0 4xx=0 5xx=0

CPU time [s]: user 8.90 system 15.77 (user 35.6% system 63.1% total 98.7%)
Net I/O: 79.8 KB/s (0.7*10^6 bps)

Errors: total 0 client-timo 0 socket-timo 0 connrefused 0 connreset 0
Errors: fd-unavail 0 addrunavail 0 ftab-full 0 other 0


I ran the tests multiple times to be sure, but it seems that Web Velocity can handle whatever I can throw at it locally quite nicely

Technorati Tags: ,

Read: Web Velocity Load Testing

Topic: Third of a year with no heart Previous Topic   Next Topic Topic: Smalltalk Daily 11/19/08: Finding UI Examples

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use