Niels,
Which version of libevent are you using and where is the code that makes use of it?
Wow -- I just checked this via Fink (Mac OSX package manager), and it indicates that it's v0.8 (read: old as dirt, since v1.1a is available). I'm going to update it and re-run my tests.
The high CPU usage is happening inside event_dispatch() -- basically, it seems to be doing a "busy wait" on connected sockets, trying to send data. This is on Debian Sarge (using epoll()) and Mac OSX 10.4.6 (using kqueue). Is there a way I can configure libEvent to not "busy wait"?
Regards, John Falling You - exploring the beauty of voice and sound http://www.fallingyou.com _______________________________________________ Libevent-users mailing list Libevent-users@monkey.org http://monkey.org/mailman/listinfo/libevent-users
