I started hacking some instrumentation into NCSA's httpd to see where it
was spending time (I couldn't find a profiling tool that would work through
the fork(), though in retrospect it probably would have been easier to run
the server in single connection mode and throw out all of the startup
stuff). NOT counting the fork() time, I found the server spending about
20-30% of its time (wall and CPU) in the code that reads the request
headers. Code like this doesn't help (getline() in util.c):
if((ret = read(f,&s[i],1)) <= 0) {
Your mileage may vary.
>Any comments and suggestions are welcome, and I do plan to make the test
>suite available when finished, as well as a result summary. Thanks!
I too am interested in performance, and am interested in whatever you come
up with. I'm also interested in stories from sites that are suffering
scalability problems, if there are any to share.
Andrew Payne
Open Market, Inc.