Hi Jay,
Followup: for now, it looks like we're just that we're being hammered
hard enough that the web server has no choice but to starts sending
503 responses. Memory usage appears bounded, despite what I had
thought earlier. I'll add additional server instances to host
wescheme.org's compiler servers and follow up with observations.
What is the current behavior of the system with regards to how it
handles a barrage of requests? I took a look at:
http://docs.racket-lang.org/web-server-internal/limit.html
which describes what one might do to apply limits to the web server.
However, I can not find documentation that states what the default
rate-limiting behavior is when using serve/servlet.
Would you be amendable to adding a #:max-waiting keyword argument to
serve/servlet to override the default backlog of 40 waiters? The
other calls into the web server provide a #:max-waiting parameter, and
I'm not sure I understand why it's absent from serve/servlet.
____________________
Racket Users list:
http://lists.racket-lang.org/users
