[hunchentoot-devel] clisp port

[Anton Vodonosov]

Hello.

Attached is the adjustment of the 
clisp port suggested by Luis Oliveira (
http://common-lisp.net/pipermail/tbnl-devel/2006-November/000815.html)
to hunchentoot 0.14.7.

I've dropped clisp-serve-event because didn't
find it useful. Just use start-server as you
do in case of single-threaded sbcl.

Edi, is it possible to commit it?

I'm using it from about hunchentoot 0.11.1,
it works OK for me (not to say i program
for hunchentoot too much, but sometimes i do).

Clisp port may be useful in at least two cases:
- If you want free lisp on windows. SBCL on windows
  has problems with sockets (for example
  http://sourceforge.net/mailarchive/message.php?msg_id=33541185225400%40webmail24.yandex.ru,
  also it doesn't close sockets and after few thousands of 
  connections windows runs out of handles). Although
  it isn't a problem for development, in fact I switch 
  freely between sbcl and clisp all the time.

- When small memory amount is available. Windows 
  task manager reports memory usage by sbcl process
  of about 60 MB when hunchentoot is loaded. For clisp 
  it's less then 25 MB.

  I've recently deployed small bulletin board I'm 
  writing to a linux VPN with 64 MB of memory. 

  The test is to serve static 200 KB file and
  request it using ApacheBench tool:
  ab -n 1000 -c 10 http://localhost:4242/static/file
  (-n is the number of requests, -c number of threads).
  In case of SBCL few such commands leads to furious 
  swapping, whole system almost hangs and finally
  linux kills SBCL with message "out of memory".
  But clisp works stable.

Best regards,
-Anton

-------------- next part --------------
A non-text attachment was scrubbed...
Name: clisp-port.diff
Type: text/x-patch
Size: 12356 bytes
Desc: clisp-port.diff
URL: <https://mailman.common-lisp.net/pipermail/tbnl-devel/attachments/20071221/81669c84/attachment.bin>