On Sat, 2006-08-05 at 16:07 +0900, Alex Young wrote:
> Zed Shaw wrote:

> In case anybody's wondering...
<snip>
> Rehearsal -------------------------------------------------------
> net/http              7.720000   1.470000   9.190000 (  9.195841)
> rfuzz                 3.040000   1.070000   4.110000 (  4.119992)
> --------------------------------------------- total: 13.300000sec
> 
>                            user     system      total        real
> net/http              7.930000   1.370000   9.300000 (  9.298725)
> rfuzz                 2.950000   1.130000   4.080000 (  4.073578)
> 

Yeah it should be faster just by virtue of having very little to it and
using a C parser.  Keep in mind that rfuzz--unlike mongrel--isn't really
designed for speed but more for letting you easily hit web servers with
any kind of request.  Another thing some folks don't notice is that all
of the HttpClient requests are "data driven".  That means you can power
RFuzz blindly from a YAML file full of strings and hashes.

Otherwise net/http has a bunch more features, but I'll slowly add them
as I need them.  I think SSL is next on the list.

> That doesn't include those speedups for net/http that went through the 
> list a couple of weeks back, though.

I'd also be curious for the same test run with the RFuzz call being done
inside a Timeout block.  RFuzz doesn't do any of that (bare metal), and
I know Timeout blocks fire up an extra thread and eat up a bit more CPU.
I'm betting that putting RFuzz inside Timeout makes it about the same
speed at net/http.


-- 
Zed A. Shaw
http://www.zedshaw.com/
http://mongrel.rubyforge.org/
http://www.railsmachine.com/ -- Need Mongrel support?