Hi I have a question regarding with this topic to, I need about 2M filedescriptors so my squid is compiled with --enable-poll and --enable-epoll. In this case which mechanism Squid will use poll or epoll? Also, for better performance for large FD, which mechanism did you recommend poll, epoll or kqueue? Thanks Best regards -----Mensagem original----- De: squid-users <squid-users-bounces@xxxxxxxxxxxxxxxxxxxxx> Em Nome De Amos Jeffries Enviada: 25 de janeiro de 2022 20:17 Para: squid-users@xxxxxxxxxxxxxxxxxxxxx Assunto: Re: [ext] Re: Absolute upper limit for filedescriptors in squid-6? On 26/01/22 03:55, Ralf Hildebrandt wrote: > * Francesco Chemolli: >> See configure --max-filedescriptors > > ... > configure: forcing default of 131072 filedescriptors (user-forced) > checking Default FD_SETSIZE value... 1024 checking for getrlimit... > yes checking for setrlimit... yes checking Maximum number of > filedescriptors we can open... 32768 > configure: Default number of filedescriptors: 131072 ... > > Yes, I set "ulimit -n 131072" before running configure > The ./configure has a 2^15 limit for the _default_ FD number. Runtime should allow configuring larger values later (sans bugs). It also depends on the I/O module selected for runtime. Make sure you avoid select(2) and poll(2) for large FD numbers. select(2) is limited to 1024. poll(2) allows numbers large enough to hit RAM and CPU limits on speed. epoll(2) is limited to ~3.5 million. kqueue(2) is technically "unlimited" but YMMV regarding bugs etc. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
