Hello Dears,
We have a strance behavior on our ASG appliance, as there is a great CPU overhead up to 70%, with a great latency on web browsing (one site request could take up to 3 to 4 minutes. When on the other side second ASG appliance with larger concurrent users number, have to issue with CPU Utilization. After we create a policy trace on sample user we found a large transaction time as below ( 59202 ms). We note that their latency before (server-in) policy checkpoint.
We couldn't simply say that it's internet connection issue as other appliance on same cluster with same internet connection link has no latency issue.
Appreciate your support!
---------------------------------------------------------------------------------------
Note below transaction timings for sample website
connection: service.name=Explicit-8080 client.address=172.25.25.55 proxy.port=8080 client.interface=1:0.1 routing-domain=default
location-id=0 access_type=unknown
time: 2020-01-22 08:52:32 UTC
unknown ssl://components.news.sky.com:443/
DNS lookup was unrestricted
origin server next-hop IP address=2.16.209.164
user: unauthenticated
authentication status='not_attempted' authorization status='not_attempted'
url.category: none@Policy;none@YouTube;News@Blue Coat
total categorization time: 1
static categorization time: 1
application.name: none
application.operation: none
application.group: none
DSCP client outbound: 65
DSCP server outbound: 65
Transaction timing: total-transaction-time 59202 ms
Checkpoint timings:
new-connection: start 1 elapsed 0 ms
client-in: start 1 elapsed 1 ms
server-out: start 2 elapsed 0 ms
server-in: start 18995 elapsed 0 ms
client-out: start 18995 elapsed 0 ms
access-logging: start 59202 elapsed 0 ms
stop-transaction: start 59202 elapsed 0 ms
Total Policy evaluation time: 1 ms
ssl server hello complete: 99
url_categorization complete time: 2
ssl_server started tunnel: 19042
server connection: start 2
DNS Lookup: start 18995 elapsed 0 ms
server connection: connected 48
client connection: first-response-byte 0 last-response-byte 59202
Total time added: 1 ms
Total latency to first byte: 47 ms
Request latency: 1 ms
OCS connect time: 46 ms
Response latency (first byte): 0 ms
Response latency (last byte): 0 ms