unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Nala Ginrut <nalaginrut@gmail.com>
To: Daniel Hartwig <mandyke@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: [PATCH] Add backlog option to http-open
Date: Fri, 5 Apr 2013 09:29:15 +0800	[thread overview]
Message-ID: <CAPjoZoe+4aQNOAxEGOeP7T0_yJgCx_jDTJ=N_ig3BrT5VxYbig@mail.gmail.com> (raw)
In-Reply-To: <CAN3veRfCCQ9p9rCz2PCobcF0KMi8F28Z+NuQ6FoyXfs2JRxapg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]

在 2013-4-5 AM8:29,"Daniel Hartwig" <mandyke@gmail.com>写道:
>
> On 4 April 2013 12:39, Nala Ginrut <nalaginrut@gmail.com> wrote:
> > Here's a patch to add backlog option to http-open, users may use it
> > like:
> >
> > -----------------------cut------------------------
> > (run-server (lambda (r b) ...)
> >             'http
> >             '(#:port 1234 #:backlog 1024))
> > -----------------------end------------------------
> >
>
> You want to be quite sure about using a much larger value here.  Of
> course, the kernel will ignore settings above its own configuration,
> but if your server reaches a backlog of 128 this already indicates a
> delay in servicing those requests.  Increasing the backlog to 1024 is
> going to substantially increase that delay, no?

That's users' consideration, we just provide mechanism.
And in practical, users will configure the kernel or modify it.

For high concurrency server, that delay is endurable, the aim is to hold
more connections.
Anyway, that's users policy. The upstream has to provide mechanism.

[-- Attachment #2: Type: text/html, Size: 1438 bytes --]

      reply	other threads:[~2013-04-05  1:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04  4:39 [PATCH] Add backlog option to http-open Nala Ginrut
2013-04-05  0:22 ` Daniel Hartwig
2013-04-06  4:14   ` Nala Ginrut
2013-04-07  6:56     ` Daniel Hartwig
2013-04-05  0:29 ` Daniel Hartwig
2013-04-05  1:29   ` Nala Ginrut [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPjoZoe+4aQNOAxEGOeP7T0_yJgCx_jDTJ=N_ig3BrT5VxYbig@mail.gmail.com' \
    --to=nalaginrut@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=mandyke@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).