Re: Five Reasons Why Synchronous Networking Is Bad
Re: Five Reasons Why Synchronous Networking Is Bad
- Subject: Re: Five Reasons Why Synchronous Networking Is Bad
- From: Mark Pauley <email@hidden>
- Date: Thu, 5 Mar 2009 11:27:25 -0800
Dude, if you're monitoring 1k network sockets with CFSocket, select is
the least of your issues.
You'll eventually hit the open fd limit, not to mention that you'll
choke the rest of the system as you'll be hogging the filesystem.
On Mar 5, 2009, at 8:20 AM, Joel Reymont wrote:
On Mar 5, 2009, at 4:00 PM, Quinn wrote:
I wouldn't say that either of these is completely true, at least
not yet. Certainly, CFSocket extracts a performance penalty on
current system software and, if you're goal is the absolute best
performance, dropping down to the BSD sockets level is definitely
the best choice.
I can't help but chime in. Using select is suboptimal when the
number of monitored file descriptors goes above 1k or so. I wish the
code behind CFSocket used kqueue and kevents instead.
---
http://tinyco.de
Mac, C++, OCaml
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_Mark
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden