Update of /cvsroot/curl/curl-www/libcurl/hiper
In directory labb:/tmp/cvs-serv1030
Modified Files:
_schedule.html
Log Message:
clarification
Index: _schedule.html
===================================================================
RCS file: /cvsroot/curl/curl-www/libcurl/hiper/_schedule.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -d -r1.16 -r1.17
--- _schedule.html 9 Dec 2005 11:18:42 -0000 1.16
+++ _schedule.html 9 Dec 2005 12:36:28 -0000 1.17
@@ -93,6 +93,14 @@
</ol>
+<p>
+ I should perhaps add that the curl_multi_fdset() invoke is also included in
+ the multi_perform() time, so there are two loops going over all
+ descriptors. One to set bits in the fd_set variables and one to check all
+ bits of the fd_set variables. So at 32000 us for 9000 connections, it loops
+ 18000 laps which makes less than 2 microseconds per lap. (Of course counting
+ time/laps is an oversimplification, but anyway...)
+
STOP
MARKDATE(Dec 7 2005) Different test/measure approach:
@@ -122,9 +130,8 @@
libcurl I've done so far but none of those changes are required for this to
run/work.
-STOP
-
- MARKDATE(Dec 6 2005) Ok, I think I'll change my measuring approach and I will
+<p>
+ Ok, I think I'll change my measuring approach and I will
instead write up my own HTTP server and control that to allow it to either
sit perfectly quiet (just keeping the connection alive) or to send an endless
stream of data. By allowing the selection of behaviour be based on the URL, I
@@ -137,10 +144,7 @@
<br>
<a href="http://monkey.org/~provos/libevent/libevent-benchmark.jpg"><img border="0" src="bench.jpg" alt="graph comparing event systems' performances"></a>
<p>
-
-STOP
-
- MARKDATE(Dec 6 2005) Been struggling to get a test program that can be used
+ I've been struggling to get a test program that can be used
to measure and show the current overhead/speed in a good way. I've been quite
surprised by the speed of the existing implementation. My test application
easily initiates and transfers 2000 simultaneous transfers (and man does this
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.