You might find out that the Ultraband Server has a High Asymmetric Percentage, which negatively affects performance and you need to fix this asymmetric issue because it affects the product's cache (memory).
Asymmetry means Cache is receiving only one path either upstream or downstream of the TCP session which is passing via cache and the other path is missing due to missing ACL in the PBR configuration. Below are examples of logs in which 1 represents upstream traffic missing and 2 represents downstream traffic missing.
To get the Asymmetric Debug Log, please create a support ticket and an agent will help you out.
To get these logs please follow the steps in the article: Identifying Asymmetric Traffic
The PeerApp system cannot produce asymmetry as it is completely passive, it can only detect asymmetry and display it on Asymmetric graphs. As mentioned before, the debug logs include the number of IPs detected by the PeerApp Cache system as asymmetric connections. After obtaining it, you must go through it and make sure that, in PBR configuration, both downstream & upstream ACL include the addresses appearing in the logs. PBR configuration needs to be tuned and it's optimal to limit asymmetric traffic below 5%.
Quick check Asymmetric rate
The picture below shows how a decrease in Asymmetric Connections looks like on the graphs.