From: "R. Tyler Croy" <tyler@linux.com>
Subject: Re: Performance techniques used in AWS
Date: 14 Jun 2011 15:10:12 GMT
Date: 2011-06-14T15:10:12+00:00 [thread overview]
Message-ID: <4df779d4$0$2211$742ec2ed@news.sonic.net> (raw)
In-Reply-To: m2fwnc3bm4.fsf@pushface.org
On Tue, 14 Jun 2011 12:18:11 +0100, Simon Wright wrote:
> "Yannick Duchêne (Hibou57)" <yannick_duchene@yahoo.fr> writes:
>
>> Le Tue, 14 Jun 2011 12:40:15 +0200, Simon Wright <simon@pushface.org> a
>> écrit:
>>> I guess the performance will depend heavily on select(2) vs poll(2) or
>>> epoll.
>> According to this
>> http://monkey.org/~provos/libevent/libevent-benchmarks.jpg and that
>> http://monkey.org/~provos/libevent/libevent-benchmark2s.jpg epoll and
>> kqueue are the more efficient
>
> I see that libev[ent] abstracts away the actual polling mechanism, which
> is good. Of course, what mechanism you can actually use depends on the
> OS: I think epoll is a Linux-specific service? - certainly no sign of it
> on this Mac.
Correct, you're options on Linux 2.6+ are epoll(2), on *BSD and Mac OS X
the kqueue(2) facility is available. For Windows users..well, you get what
you pay for ;)
Both libev and libevent both abstract away the underlying polling
mechanism.
--
- R. Tyler Croy
--------------------------------------
Code: http://github.com/rtyler
next prev parent reply other threads:[~2011-06-14 15:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 5:48 Performance techniques used in AWS R. Tyler Croy
2011-06-13 8:06 ` Thomas Løcke
2011-06-13 16:28 ` Pascal Obry
2011-06-13 16:34 ` Pascal Obry
2011-06-14 4:37 ` J-P. Rosen
2011-06-14 5:14 ` R. Tyler Croy
2011-06-14 8:28 ` Natasha Kerensikova
2011-06-14 10:41 ` Yannick Duchêne (Hibou57)
2011-06-14 10:40 ` Simon Wright
2011-06-14 10:48 ` Yannick Duchêne (Hibou57)
2011-06-14 10:51 ` Yannick Duchêne (Hibou57)
2011-06-14 11:18 ` Simon Wright
2011-06-14 15:10 ` R. Tyler Croy [this message]
2011-06-14 15:31 ` Yannick Duchêne (Hibou57)
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox