Hi, for its own design, select call can handle up to 1024 elements, no matter what ulimit says.
WARNING: select() can monitor only file descriptors numbers that are less than FD_SETSIZE (1024)—an unreasonably low limit for many modern applications—and this limitation will not change. All modern applications should instead use poll(2) or epoll(7), which do not suffer this limitation.
More than 1024 connections makes select to crash within the websocket.
Can it be convertible in pool() or epool()??
Hi, for its own design, select call can handle up to 1024 elements, no matter what ulimit says.
WARNING: select() can monitor only file descriptors numbers that are less than FD_SETSIZE (1024)—an unreasonably low limit for many modern applications—and this limitation will not change. All modern applications should instead use poll(2) or epoll(7), which do not suffer this limitation.
More than 1024 connections makes select to crash within the websocket. Can it be convertible in pool() or epool()??