> Yes, 'epoll' is the most efficient mechanism on Linux. I recommend using > level-triggered events because it's simpler.
That's the opposite as to what I have done. :) From what I have read I gathered that Event Triggered is MUCH faster. But I guess I could have gotten it all wrong. > More generally talking about the way little mistakes can cause your process > to consume absurd amounts of CPU. For example, as the number of connections > goes up, how you locate a connection, how much memory you allocate per > connection, and how many context switches you force all start to become > significant. Do you have any pointers or know of a good article somewhere which has? :) > It is absolutely not atomic. TCP is a byte-stream protocol that does not > preserve message boundaries, period. That said, you can certainly > *optimize* for the most common case, which will likely be an MTU of 1500 or > so and as much data packed into the first receive as possible. But trust > me, if you rely on it, sooner or later your code will break. Yeah that's the common answer I got. Seems just about right. Thanks for your replies /Tommy Wallberg ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
