News for hackers. Stuff that matters.
Re:Shoestring Budget? Starting to feel growth issues on you... by cliff on Wednesday September 10, 2008 @11:20PM (#301037)
Maybe I'm missing something -- if you're I/O-bound why would it matter whether you use epoll() vs poll() other than CPU usage?

From what I understand (and how I've used it in my work), one uses epoll() specifically because they're NOT I/O-bound and so need to come up with strategies for using the minimum amount of CPU and RAM per simultaneous I/O so as to avoid becoming CPU- or RAM- bound.

Hence my original point -- if one is I/O-bound while using poll(), it doesn't really matter whether the CPU is spinning on that or epoll(), since I/O won't happen any faster.

Re:Shoestring Budget? Starting to feel growth issues on you... by spc476 on Thursday September 11, 2008 @01:04AM (#301129)
I just found epoll() much easier to work with than select() (been there, done that, rather not go back to it) or poll(), and the fact that you avoid scanning an array upon return.