| NowWap sizing on HP Proliant DL360G5 |  Search
|
|
NowSMS Support Forums ⬆ Now.WAP Proxy Support ⬆ |
◄ ► |
| Author | Message | |||
| William Tiew New member Username: Williamtiew Post Number: 1 Registered: 03-2011 |
Dear NowSMS Support, Currently, our NowWap presents the following profile: -Hardware:HP Proliant DL360G5 XEON (R)CPU 5110@ 1.6GHz (Dual Core) 4GB of RAM,80GB HDD - WAP version v2010.02.01 - License is 25 concurrent Active Users. We would like to know what would be the limitations in terms of volume, throughput and even performance for this HW spec. Those information will be very useful to us specially if we have to implement new projects that would require high resource usage. Your assistance on this matter will be more than appreciated. Thank you in advance. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3028 Registered: 08-2008 |
Hi William, I'd be comfortable scaling that system up to 1000 concurrent users. -- Des NowSMS Support | |||
| William Tiew New member Username: Williamtiew Post Number: 2 Registered: 03-2011 |
Dear Des, thanks for the prompt and answer, will stick on this limit. By the way, do you mind to explain more on below parameter: 1. current user: how NowWap definition Current user? does current user rely on HTTP request or radius_accounting_start? 2. License on NowWap based on Active user, i had configure below two parameter=ZERO, but notice NowWap didn't release Active user counter even user had disconnect(PDP context closed), what is the gap(duration) for NowWap to release the counter of Active user? a. Maximum keepalive for client connection=0 b. Maximum keepalive for internet connection=0 Appreciate your patient on this. Thank you. Rgds, William | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3033 Registered: 08-2008 |
Hi William, User session isn't counted until there is an HTTP request. Radius accounting disconnect (usually associated with PDP disconnect) is normally what releases a session, otherwise there is an inactivity timeout of 5 minutes. -- Des NowSMS Support | |||
| William Tiew New member Username: Williamtiew Post Number: 3 Registered: 03-2011 |
Dear Des, below two parameter are configure to handle inactivity timeout right? a. Maximum keepalive for client connection=0 b. Maximum keepalive for internet connection=0 in case i have configure as above, can i say release of user counter on license is immediate after pdp stop receive by NowWap? no more waiting for 5minutes, correct? Thank you. Rgds, William | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3034 Registered: 08-2008 |
Hi William, Those two parameters do not have a direct effect. User session release is immediate upon receipt of radius accounting disconnect. (No wait for inactivity timeout.) -- Des NowSMS Support | |||
| William Tiew New member Username: Williamtiew Post Number: 4 Registered: 03-2011 |
Dear Des, let me correct my understanding. License on NowWap: 1. current-user counter will rely on HTTP_GET request for user, not relate to radius_accounting_start 2. current-user will increase 1 if user have valid radius_accounting_start and initiate HTTP_GET. this condition must be fulfill in order for NowWap to increase one counter for Active user. 3. NowWap will keep monitor on radius_accounting_stop against active user via msisdn parameter. 4. if NowWap receive rad_accounting_stop for that msisdn, it will immediate reduce active-user counter. 5. after NowWap release active user counter, any tcp/http stream from internet to mobile IP will not be entertain by NowWap which have no impact to increase/decrease of Current user counter can confirm above statement are correct? Thank you. Rgds, William | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3035 Registered: 08-2008 |
Correct. For #2 to work exactly like you describe does require the "Require MSISDN for all requests" setting to be enabled, which is a normal setting for an operator gateway. | |||
