Talk:C10k problem

From Wikipedia, the free encyclopedia
Jump to: navigation, search


Hi, I think deletion is not the answer. Really there are few references for C10k [I think the only good one is]. The solution were to write a good article and finding C10k references. So I vote -1 for deletion.

FYI, the deletion discussion as going on at Wikipedia:Articles_for_deletion/C10k_problem. But as long as you wrote here: Please see WP:Notability. If there are few references for something—indeed, if only one person has expounded on the topic (and that person didn't actually say anything about the topic: he just claimed it, and went on to list a bunch of ways to improve capacity that don't depend on there being a specific existing capacity limit)—then that's a sign that the topic may not be an appropriate basis for an article on Wikipedia. —Largo Plazo (talk) 20:37, 14 December 2009 (UTC)

1022 client problem[edit]

Calling it C10k is misleading, as its really a 1022 client problem, on most operating systems. The reason for this problem is how select(2) is implemented. Any process that has more open files than FD_SETSIZE might cause FD_SET(2) or select(2) to cry or to crash. This limit is 1024 under Linux, so maximum number of clients that can be handled by a process using select(2) is 1021, if this process has no other files open. The effective number of clients select(2) can handle is likely much lower, when the process also opened other files. The solution is to use epoll(4) instead. (talk) 07:17, 23 January 2012 (UTC)


The last section about Whatsapp etc. is not that clear... -- (talk) 14:24, 10 June 2016 (UTC)