From: michi1@michaelblizek.twilightparadox.com (michi1 at michaelblizek.twilightparadox.com)
To: kernelnewbies@lists.kernelnewbies.org
Subject: MAX limit of file descriptor
Date: Tue, 12 Feb 2013 06:45:14 +0100 [thread overview]
Message-ID: <20130212054514.GA2239@grml> (raw)
In-Reply-To: <61126.1360610656@turing-police.cc.vt.edu>
Hi!
On 14:24 Mon 11 Feb , Valdis.Kletnieks at vt.edu wrote:
> On Sat, 09 Feb 2013 13:10:47 +0800, horseriver said:
...
> > In network programing ,what is the essential for the maximum of connections
> > dealed per second
> ...
> So the *real* question
> becomes "how many times per second is your box able to fork() off an httpd,
> do all the processing required, and close the connection?"
If you fork(), than this definitely will be your bottleneck (except the
application does something even slower). Better use epoll+nonblocking i/o.
-Michi
--
programing a layer 3+4 network protocol for mesh networks
see http://michaelblizek.twilightparadox.com
next prev parent reply other threads:[~2013-02-12 5:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-09 5:10 MAX limit of file descriptor horseriver
2013-02-09 15:49 ` Peter Teoh
2013-02-09 17:08 ` Gaurav Jain
2013-02-09 17:09 ` Gaurav Jain
2013-02-10 22:07 ` horseriver
2013-02-11 17:16 ` Mulyadi Santosa
2013-02-11 19:36 ` Valdis.Kletnieks at vt.edu
2013-02-10 12:29 ` michi1 at michaelblizek.twilightparadox.com
2013-02-10 14:47 ` Peter Teoh
2013-02-10 17:50 ` michi1 at michaelblizek.twilightparadox.com
2013-02-11 19:24 ` Valdis.Kletnieks at vt.edu
2013-02-12 5:45 ` michi1 at michaelblizek.twilightparadox.com [this message]
2013-02-12 9:31 ` Peter Teoh
2013-02-12 9:38 ` Peter Teoh
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130212054514.GA2239@grml \
--to=michi1@michaelblizek.twilightparadox.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.