We are using our 2 Aruba controllers to redirect users to an external portal. We service up to 50,000 unique clients per day so I'm guessing some manual config of the internal web-server could be usefull.
Since we're using 2x 7220 controllers the web-max-clients defaults to 75 concurrent clients.
When I pull up the statistics it seems I never have any available connection slots. Regardless of this, the portal redirect doesn't appear slow or anything.
show web-server st
Web Server Statistics:
----------------------
Current Request Rate: 23 Req/Sec
Current Traffic Rate: 2 KB/Sec
Busy Connection Slots: 75
Available Connection Slots: 0
Total Requests Since Up Time: 43762818
Total Traffic Since Up Time: 15443592 KB
Avg. Request Rate Since Up Time: 3 Req/Sec
Avg. Traffic Rate Since Up Time: 1311 Bytes/Sec
Server Scoreboard RRRWRRWRCCRCRRRCRCRRRRRCRCCRRCCCCCCRRWRRRRCRRRRCCRCRCRRRRCRRCRRRCRWRRRCRRRC
Scoreboard Key: _ - Waiting for Connection, s - Starting up
R - Reading Request, W - Sending Reply
K - Keepalive, D - DNS Lookup
C - Closing connection, L - Logging
G - Gracefully finishing, I - Idle cleanup of worker
. - Open slot with no current process
Since cpuload seems minimal I'm thinking about increasing the web-max-clients. Is there any reason not to do this as long as cpuload isn't an issue?
Second question, the external portal guys are complaining they get a ton of requests without the max address in the url.
I vaguely remember that the controller treats certain traffic differently to lower cpu load. I cannot seem to find anything on this to corroborate this though. Can anybody confirm this/point me in the right direction on this?