Liste des Groupes | Revenir à c arch |
Chris M. Thomasson wrote:I never tried APC wrt IO and a socket server on windows before! I have created several types wrt the book I finally found on the wayback machine. IOCP was the thing to use.On 5/19/2024 3:08 PM, Chris M. Thomasson wrote:Thanks. I have never used the thread-per-client model in my servers.On 5/19/2024 3:04 PM, Chris M. Thomasson wrote:>On 5/19/2024 2:55 PM, Chris M. Thomasson wrote:>
[...]I remember a little test that Microsoft made wrt 50,000 concurrent OVERLAPPED ops in IOCP vs an event driven model actually creating a windows event per connection multiplexing WFMO in several threads. The event model did not perform as well, but it did not do too bad either. I wonder if I can still find that paper. Back in 2002 or something. Hard to remember right now.>
I am having trouble finding it. I do remember:
>
https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-2000-server/cc959494(v=technet.10)?redirectedfrom=MSDN
>
I just found an old post from me back in 2003 with a link to the paper:
___________________
You can get 50,000+ concurrent connections using IOCP, check out the
following link:
>
http://www.microsoft.com/mspress/books/sampchap/5726a.asp?#128
>
You do have to do some memory management to get there, like posting zero
byte receives to ensure that pending recvs don't lock their buffers, you can
also restrict the amount of pending sends the server has all together
[...]
___________________
The way back machine found it, I think!
>
https://web.archive.org/web/20030216222720/https://www.microsoft.com/mspress/books/sampchap/5726a.asp#128
>
Nice!
I have been using async I/O and Asynchronous Procedure Calls (APC)
for I/O completion on Windows for 30+ years. IO Completion Ports (IOCP),
which were added to Windows later, have similar functionality
(perhaps IOCP might have slightly better scaling with many cores).
Les messages affichés proviennent d'usenet.