[hunchentoot-devel] Hunchentoot performance

[vseguip at gmail.com]

Hi Edi,

> You're on SBCL?  Try to benchmark RFC-1123-DATE with pretty-printing
> turned off.

That sure helped, I'm now in he 510~550 req/sec range. Anyway, is
there a more elegant way to turn logging off than simply redefining
the method? I think the fact that log-message is locking when logging
to a file makes it take a sever performance hit, maybe the use of a
logging framework that solves this would be nice.

> Right.  All you need now is a website with 400 visitors per
> second... :)
>
That's a piece of cake, just run apache-bench in a forever loop :).


On a side note, I wanted to comment some refactoring to hunchentoot
that I think may make sense. Right now process-connection is a
function that takes care of reading from the client, be it via
mod_lisp or directly, binding the chunga/flexi-streams if needed and
dispatching it. I think a better design would be to make
process-connection a generic method on class connection and then
implementing  methods for mod_lisp/standalone/fastcgi/whatever. Chunga
and flexi-streams wrapping could be implemented as mixins so the user
can choose to create a FCGI connection with flexi but not chunga, etc.
With this we can allow for custom backends to be developed by users so
we gain flexibility (and maintainability) at the cost of some overhead
when dispatching. What do you think?



Cheers,
  V Segui