I don't want answer related to processors. I want the number you actually want to support. Then when knowning those numbers, one can think about an architecture needed to support it. So the questions remains open: - How many concurrent users do you have to support ? - How many requests per second do you have to sustain (average value) ? - What is the total thruput needed (Bytes/Sec) ? I can add this question: - What is the maximum allowed latency time ?
This being said, 10 users per server is normally very small number unless the user are asking a lot of data or number crunching processing. > If session timeout is set to 10 min, The question is: why would a session be 10 minutes ? Why not 10 seconds or 10 hours ? You have to tell more about your application if you want good advice. > Max. 50Kb/sec for 1 request Then how long is a request ? You should not give thruput for a request but data size involved in a request. And remember we are only interested in the AVERAGE value ! > In total, I assume 500 Kb/sec per server. 500 kilo-bit-per-second is not big. Any personal computer is able to handle this. -- Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html -- [EMAIL PROTECTED] Author of ICS (Internet Component Suite, freeware) Author of MidWare (Multi-tier framework, freeware) http://www.overbyte.be ----- Original Message ----- From: "S.Korotky" <[EMAIL PROTECTED]> To: "ICS support mailing" <firstname.lastname@example.org> Sent: Monday, March 20, 2006 12:56 PM Subject: Re: [twsocket] Scalable web-based application: with or without ICSand how? > > Questions: > Hm. I can answer to your questions only as it is planned, because the > application > is being tested in 1-server configuration now with a low load. > > > - How many concurrent users do you have to support ? > In an ordinary 1-processor configuration, the single server should be capable > to process at least 10 users simultaneously. As for overall user count, > am I right that it will be as much as 10*N, where N is a number of > servers in cluster? > > > - How many requests per second do you have to sustain (average value) ? > 10, for 1-server configuration, if I understand you properly, but I'm not > sure. > If session timeout is set to 10 min, then the application may hold up to > 6000 sessions every moment. We hope this will work with 500Kb (max) > per-session data on 4Gb RAM. > > > - What is the total thruput needed (Bytes/Sec) ? > Max. 50Kb/sec for 1 request. In total, I assume 500 Kb/sec per server. > > Best wishes, > Stanislav Korotky, > Russia, Moscow, GMT +3.00 > > -- > 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