First solution seems better to me. You can also have a mix of the two solutions. For example having 8 concentrators with 2000 users and 2 servers. This will allow easy fault tolerance. The concentrators would connect randomly to one of the two servers and if one is down, connect to the other. The client application can also apply the same fault tolerant or load balancing system: they would have a prefered concentrator and one or more fallback concentrators. Concentrators could also communicate (maybe thru the servers) with each other to redirect client to another one should another one be less loaded. All that is not very difficult to implement.
-- [EMAIL PROTECTED] Author of ICS (Internet Component Suite, freeware) Author of MidWare (Multi-tier framework, freeware) http://www.overbyte.be ----- Original Message ----- From: "Dod" <[EMAIL PROTECTED]> To: "ICS support mailing" <[email protected]> Sent: Tuesday, January 03, 2006 10:41 AM Subject: [twsocket] OT rather big project question > Hello, > > I am starting a re-write one of my ICS-based server to be able to > handle 15.000 permanent cnx smoothly. The datas Clients will > send/receive will be only 2KB packets time to time. > > As Windows OS is limited with sockets and handle (whenever you can do > some tricky changes in registry) I have decided to split connections. > > Now I am wondering which solution could be the best : > > - Multiple concentrators that accept between 2000/5000 connections, > each concentrator (quite simple small application) will do only one > connection to Main server that use SQL database (MySQL for example). > If main server is down users are still connected to concentrator that > will notify users and wait until server is up again without. > > - Multiple Servers accepting 2000/5000 connections each, each server > connect to SQL datbase. When there is a server maintenance, it will > drop down all user's the client application will try reconnect until > server is up again. > > Both solution permit to split data traffic across switched network so > it will lower general bandwidth. > > I think I will use MySQL that should be enought and will have to > manage 1 or 10 max connections at same time dependig if I choose first > or second solution. > > First solution may permit smoother server updates as client part stay > always connected to concentrator and it's concentrator that will keep > connection to main server. > > Do you have any idea/advice ? > > Regards. > > -- > To unsubscribe or change your settings for TWSocket mailing list > please goto http://www.elists.org/mailman/listinfo/twsocket > Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
