That is fabulous, I have been contemplating two connection models:
(1) Keep and maintain each session connection in client lift time.
(2) Open / close the session connection frequently on demand of each
data transfer.
While (1) is my preference, it'll depend on the performance, which
connection model do you use?
Thanks Richard and Vinnie.
- jhh
On 12/24/18, Richard Hodges via Boost
I've managed 100,000 simultaneous tcp connections to a c++ server using boost::beast/asio on an appropriately configured fedora linux host.
ASIO's memory overhead is minimal if written nicely.
On Sun, 23 Dec 2018 at 01:06, Vinnie Falco via Boost
wrote: On Sat, Dec 22, 2018 at 3:01 PM hh h via Boost
wrote: What will be the maximum connections a single ASIO TCP socket server can handle?
Asio doesn't contain magic or reinvent the wheel here, `basic_socket` is a very thin abstraction over a file handle representing a socket. You need to look to the limits of your operating system and configuration to know the baseline limit. And of course subtract from that any additional per-connection resources that your application uses.
Regards
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- Richard Hodges hodges.r@gmail.com office: +442032898513 home: +376841522 mobile: +376380212 (this will be *expensive* outside Andorra!) skype: madmongo facebook: hodges.r
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost