[xSocket-develop] production level socket server pitfalls
Status: Inactive
Brought to you by:
grro
|
From: Kevin B. <kev...@go...> - 2010-02-19 08:47:20
|
Hello,
For a production level socket server what are the potential pitfalls
that I have to consider :
1. I have started the server as per the tutorial on the homepage using
IServer srv = new Server(8090, new TestHandler());
srv.run();
2. The TestHandler class implements the following interfaces
IDataHandler, IConnectHandler, IDisconnectHandler,
IIdleTimeoutHandler, IConnectionTimeoutHandler.
3. I haven't set any "System Properties" as yet and "FlushMode.ASYNC"
is not set.
4. Connection and Idle timeout's are set to default.
I have uploaded this to my VPS host. However before letting it loose in
production I wanted to test it for reliability and scalabity. Any
suggestions here would be welcome.
Memory is another aspect , My VPS host has allotted me 1GB ram with
around 8GB burst capability, is this sufficient. (As of now I have only
500MB free)
My clients would be continuously connected to the server 24x7, how much
resource would each client connection take up in terms of ram, if 1000
or more clients would be connected how do I compute the amount of ram
that would be necessary to safely run the socket server.
Please suggest other points that I have missed out here.
Regards,
Kevin
|