# Eventports

**URL:** <https://www.ruby-forum.com/t/eventports/146631>\
**Category:** NGINX\
**Created:** [August 23, 2008, 7:40am UTC](https://www.ruby-forum.com/t/eventports/146631 "2008-08-23T07:40:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mike](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/58f4c7/32.png) [@mike](https://www.ruby-forum.com/u/mike)\
**Post date:** [August 23, 2008, 7:40am UTC](https://www.ruby-forum.com/t/eventports/146631/1 "2008-08-23T07:40:37Z")

</div>

Someone on #nginx blogged about this…  
[http://letsgetdugg.com/view/Nginx\_hidden\_performance\_option](http://letsgetdugg.com/view/Nginx_hidden_performance_option)

Wondering what OSes would benefit from this? and at what point would  
it help to turn on, or should it be on always, or should it never be  
on unless you plan on doing X connections per second?

Thanks

---

<div class="post-metadata">

**Author:** ![mike](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/58f4c7/32.png) [@mike](https://www.ruby-forum.com/u/mike)\
**Post date:** [August 23, 2008, 8:04am UTC](https://www.ruby-forum.com/t/eventports/146631/2 "2008-08-23T08:04:00Z")

</div>

On Fri, Aug 22, 2008 at 10:33:50PM -0700, mike wrote:

> Someone on #nginx blogged about this…  
> [http://letsgetdugg.com/view/Nginx\_hidden\_performance\_option](http://letsgetdugg.com/view/Nginx_hidden_performance_option)
> 
> Wondering what OSes would benefit from this? and at what point would  
> it help to turn on, or should it be on always, or should it never be  
> on unless you plan on doing X connections per second?

The eventport method is available since 0.4.3:

Changes with nginx 0.4.3 26 Sep  
2006

```
*) Feature: the Solaris 10 event ports support.

```

It can be used on modern Solarises only. The similar methods are  
kqueue (FreeBSD, MacOSX, NetBSD, OpenBSD) and epoll (Linux).

However, event ports have (or may be already had) some bugs: one of them  
leads to panic, another stops accepting connections. This is the reason  
why on Solaris nginx uses /dev/poll method as the best one.

---

<div class="post-metadata">

**Author:** ![mike](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/58f4c7/32.png) [@mike](https://www.ruby-forum.com/u/mike)\
**Post date:** [August 27, 2008, 8:12am UTC](https://www.ruby-forum.com/t/eventports/146631/3 "2008-08-27T08:12:22Z")

</div>

Ya, I learned that the hard way. Our production nginx server stopped  
accepting connections after a day of use. I might need to look into  
improving eventports support on solaris.

-Victor

Igor S. wrote:

> On Fri, Aug 22, 2008 at 10:33:50PM -0700, mike wrote:
> 
> > Someone on #nginx blogged about this…  
> > [http://letsgetdugg.com/view/Nginx\_hidden\_performance\_option](http://letsgetdugg.com/view/Nginx_hidden_performance_option)
> > 
> > Wondering what OSes would benefit from this? and at what point would  
> > it help to turn on, or should it be on always, or should it never be  
> > on unless you plan on doing X connections per second?
> 
> The eventport method is available since 0.4.3:
> 
> Changes with nginx 0.4.3 26 Sep  
> 2006
> 
> ```
> *) Feature: the Solaris 10 event ports support.
> 
> ```
> 
> It can be used on modern Solarises only. The similar methods are  
> kqueue (FreeBSD, MacOSX, NetBSD, OpenBSD) and epoll (Linux).
> 
> However, event ports have (or may be already had) some bugs: one of them  
> leads to panic, another stops accepting connections. This is the reason  
> why on Solaris nginx uses /dev/poll method as the best one.

---

<div class="post-metadata">

**Author:** ![mike](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/58f4c7/32.png) [@mike](https://www.ruby-forum.com/u/mike)\
**Post date:** [August 27, 2008, 8:33am UTC](https://www.ruby-forum.com/t/eventports/146631/4 "2008-08-27T08:33:20Z")

</div>

On Wed, Aug 27, 2008 at 08:12:22AM +0200, Victor I. wrote:

> Ya, I learned that the hard way. Our production nginx server stopped  
> accepting connections after a day of use. I might need to look into  
> improving eventports support on solaris.

On the basis of I saw in debug log this is Solaris bug: nginx always  
registers an event on listen socket after it has accepted a new  
connection,  
but sometime the event is not triggered.
