> Yep, I am a java poser, but I'm trying hard to learn new tricks :-)
I did *not* say that. LOL
> I welcome some good hearty discussion on this topic. Chuck and Victor
> have convinced me that BSF is just not the right solution for script
> enabling JSP's but they might be making some faulty assumptions.
I don't know if we're talking about "faulty" assumptions, so much as just
different ones. For example, all three of you are HTTPD developers who also
work on BSF, whereas Sanjiva works more with Java-based web services and
BSF.
Benchmarking, as I've done recently, Apache -> mod_jk2 (UNIX domain
sockets) -> Tomcat 4.1, shows the somewhat expected *huge* difference in
performance between httpd and tomcat.
Server Software: Apache/2.0.40 Apache/2.0.40
Server Hostname: tomcat httpd
Server Port: 80 80
Document Path: / /
Document Length: 3779 bytes 5979 bytes
Concurrency Level: 50 50
Time taken for tests: 41.067 seconds 8.653 seconds
Complete requests: 10000 10000
Failed requests: 0 0
Broken pipe errors: 0 0
Keep-Alive requests: 0 0
Total transferred: 40210000 bytes 62866692 bytes
HTML transferred: 37790000 bytes 59891643 bytes
Requests per second: 243.50 [#/sec] (mean) 1155.67 [#/sec] (mean)
Time per request: 205.34 [ms] (mean) 43.27 [ms] (mean)
Time per request: 4.11 [ms] 0.87 [ms] [across
concurrent requests]
Transfer rate: 979.13 7265.31 [Kbytes/sec]
received
Performance is certainly relative. Even using If-Modified-Since, for which
I have support in most of my dynamic content generation pages, the
performance improvement is only double, and the CPU load remains high:
Requests per second: 395.41 [#/sec] (mean)
Time per request: 126.45 [ms] (mean)
Time per request: 2.53 [ms] (mean, across all concurrent requests)
Transfer rate: 51.40 [Kbytes/sec] received
However ... relating back to the discussion at hand, this appears to suggest
that the vast majority of the overhead of serving a JSP page is not the page
execution, itself. The 304 handling short-circuits the JSP page in the
service() method; the page ISN'T executed, and the 304 code is immediately
returned.
I have not benchmarked tomcat directly at this time, so I can't tell you if
the overhead is inside of Tomcat, or in the connector. I'll cc Costin to
see if he cares to shed any light on that specific topic.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
