View source

==0k test==

We want to make sure Resin can handle as many concurrent connections as possible without glitches or blocking. The tiny 0k file is a good test for high concurrency, because it spends less time on network overhead and more time stressing the threading and internal locks. Because we used an 8-core machine, we can be certain that we're avoiding unnecessary locks or timing problems.

For most sites, the small file stress test simulates heavy ajax use, and small file use. As sites become more interactive, this small file test becomes ever more important.

As a comparison of a threaded Java web server with an event-based C web server, the 0k test is a good test of the threading and event manager dispatch. Because most of the time in the test is establishing a connection or switching between requests at the very highest rate, both the threading and the event management get a tough work-out.

===Command Line Arguments===

====0k.sh====
<pre>
./admin.sh 300000 2000 20000 1000 0k
</pre>

====admin.sh====
<pre>
autobench_admin
--clients xen:4600,lancre:4600
--uri1 /file_$5.html
--host1 ch_resin --port1 8080
--uri2 /file_$5.html
--host2 ch_nginx --port2 80
--num_conn $1
--num_call 10
--low_rate $2
--high_rate $3
--rate_step $4
--timeout 3
--file out_con$1_start$2_end$3_step$4_$5.tsv
</pre>

Above is used to setup 300,000 connections at a rate of 20,000 to 200,000 requests per second.
Each iteration increases the rate by 10,000 from 20,000 to 200,000.

===0k html file file_0k.html===
<pre>
 &lt;html> 
 &lt;body>
 &lt;pre>&lt;/pre>
 &lt;/body>
 &lt;/html>
</pre>

=== 0k full Results for 0K test ===

[[Image:Resin_nginx_0k_full2.png]]

[[Image:Resin_nginx_response_time.png]]

[[Image:Nginx_resin_0k_IO_throughput.png]]

[[Image:Nginx_resin_errors_0k.png]]