Rank: Member
Groups: Member
Joined: 4/27/2008
Posts: 6
Points: 18
Location: Lagos, Nigeria
|
Hi,
Presently i have a solution that uses Socket and SocketAsyncArgs (new from .net35) to open multiple client connections to a TCP resource.
It works fine in testing, but i am worried about the limitations it will face in production with >10000 connected clients. My concerns are:
1) Memory consumption - since each open socket uses up non-shared memory
2) Performance - since we plan on scaling out using several low-end boxes
3) Windows 65k port limitation
Please how can XF.Network be employed in this circumstance.
Regards.
Charles.
|
Rank: Administration
Groups: Administration
Joined: 2/15/2008
Posts: 130
Points: 835
|
Hi,
1. XF.Network consumes less memory then .NET Socket, non-shared memory is most consumed when there are too many pending operations.
2. XF.Network uses less CPU time, which is a better choice for low-end boxes.
3. 65k port limitation is per network interface, so if your box has several network interfaces it may handle more concurrent connections.
|
