On 26.10.2005., at 05:31, Sébastien Arnaud wrote:
Server Software: Cherokee/0.4.27
Server Hostname: localhost
Server Port: 8181
Document Path: /
Document Length: 1456 bytes
Concurrency Level: 10
Time taken for tests: 16.061 seconds
Complete requests: 50000
Failed requests: 0
Broken pipe errors: 0
Keep-Alive requests: 49911
Total transferred: 84255699 bytes
HTML transferred: 72807280 bytes
Requests per second: 3113.13 [#/sec] (mean)
Time per request: 3.21 [ms] (mean)
Time per request: 0.32 [ms] (mean, across all concurrent
requests)
Transfer rate: 5245.98 [Kbytes/sec] received
The good news is that the numbers are pretty sweet even if just
synthetic. (btw this is on a 7450 PPC G4 @ 1.67Ghz)
great!
I got the following output from the console where cherokee was
launched:
Cherokee Web Server 0.4.27: Listening on port 8181, TLS disabled,
IPv6 disable
using kqueue, 12288 fds limit, 5 threads, 2457 fds in each
FIFO scheduling policy
fdpoll-kqueue.c/171: ERROR: kevent: Bad file descriptor
fdpoll-kqueue.c/171: ERROR: kevent: Bad file descriptor
fdpoll-kqueue.c/171: ERROR: kevent: Bad file descriptor
fdpoll-kqueue.c/171: ERROR: kevent: No such file or directory
fdpoll-kqueue.c/171: ERROR: kevent: Bad file descriptor
fdpoll-kqueue.c/171: ERROR: kevent: Bad file descriptor
fdpoll-kqueue.c/171: ERROR: kevent: Bad file descriptor
fdpoll-kqueue.c/171: ERROR: kevent: Bad file descriptor
fdpoll-kqueue.c/171: ERROR: kevent: Bad file descriptor
fdpoll-kqueue.c/171: ERROR: kevent: Bad file descriptor
I had never seen the "no such file or directory" before though.
Marko, did you see this one as well?wwww
yes, but I thought it was gone with the fix on content-length but
obviously was not.
the problem seems to be that kqueue specifications says that kqueue
should not notify events on closed file descriptors, but
perhaps the macosx implementation is not conforming.
http://people.freebsd.org/~jlemon/papers/kqueue.pdf
however I'm not sure. Maybe the specification says that it should
return the error. Someone tried it on a freebsd?
<quote>
[...]
a socket, in turn generating an event. However, before
the application is notified of this pending event, it per-
forms a close() on the socket. Since the socket is no
longer open, the event should not be delivered to the ap-
plication, as it is no longer relevant.
</quote>
Marko_______________________________________________
Cherokee mailing list
[email protected]
http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee
