Re: [Chicken-users] performance issue in xml-rpc

[Daishi Kato]

Hi,

Thank you for your comment.
I first modified http-server.scm to write HTTP headers all at once,
but it didn't help much or none.

Then, I enabled buffering at tcp.scm, which works pretty fine.

What I did is the following:
Just add this
(http:listen-procedure
(lambda args
  (tcp-buffer-size 1000)
  (apply tcp-listen args)))
before
((http:make-server 60234))

And now, it takes only less than 4ms for each request. (10+ times faster!)

I also remember the talk of adding output-buffering to http-server,
but how is this different from it?

Daishi

On 12/6/06, Graham Fawcett <address@hidden> wrote:
> Daishi,
>
> OK, I've only done a five-minute test of xml-rpc-server -- but yes, I
> think that using (1) TCP_NODELAY, (2) TCP_CORK on Linux or (3)
> buffering output in http-server before transmitting to the socket
> would improve performance, esp. for smaller messages. I ran your test
> server, and watched the traffic in a packet-analyzer. Http-server is
> sending loads of small packets, esp. when outputting the HTTP header.
>
> There was talk of adding output-buffering to http-server, but I don't
> remember where this discussion left off.
>
> Graham