During access testing and online operations, if you encounter lag, application crashes, black screens, or blurred images, it is necessary to locate the issue by combining multiple data metrics. The console offers the session status query feature, which allows searching for session information within 14 days by entering the UserId or RequestId.
Data Metrics and Interpretations
RTT (ms):
Network latency metric Round-Trip Time (RTT) is an important parameter for measuring network performance. It represents the total time required for a data packet to travel from the sender to the receiver and back. If this metric is high or shows fluctuations, it indicates poor network conditions on the user's side.
GPU Usage (%):
If the GPU usage rate remains high during this connection, issues such as application lag, low rendering frame rates, and occasional application crashes may occur. It is recommended to switch to a concurrent model with a higher graphics card configuration or optimize the application to reduce GPU performance overhead.
CPU Usage (%):
If the CPU usage rate remains high during this connection, issues such as application lag, low rendering frame rates, and occasional application crashes may occur. It is recommended to switch to a concurrent model with more CPU cores or optimize the application to reduce CPU performance overhead.
Memory (%):
If the memory usage rate remains high during this connection, issues such as application lag and application crashes may occur. It is recommended to check for situations such as memory overflow and stack due to untimely task cleanup, and consider switching to a concurrent model with higher memory.
Frame Rate (FPS):
If the capture frame rate is too low, it may cause lag and other issues. This indicates that the current concurrency specification is insufficient to handle the load. It is recommended to use a higher specification of concurrency. When the capture frame rate is below 30 FPS, to stabilize the frame rate, Cloud Application Rendering (CAR) will insert duplicate frames to fill the encoding frame rate up to 30 FPS (without causing additional delay). A low frame rate is usually the result of other causes, and needs to be analyzed in conjunction with the CPU/GPU/memory usage rate at the same time, as well as application runtime logs.
Video Uplink Bitrate (Kbps)
Displays the bitrate for video uplink transmission. The CAR client SDK can collect data from the local camera and package it as input for the virtual camera on a cloud machine. If the local SDK device has the camera feature enabled, this data can be queried.
Video Downlink Bitrate (Kbps)
Displays the bitrate for cloud image transmission. If the bitrate is unstable or too low, it can cause the user to see a blurred image. This may be related to the user's local network conditions or the bitrate range settings of the project.
Audio Uplink Bitrate (Kbps)
Displays the bitrate for audio uplink transmission. The CAR client SDK can collect data from the local microphone and package it as input for the virtual microphone on a cloud machine. If the local SDK device has the microphone feature enabled, this data can be queried.
Audio Downlink Bitrate (Kbps)
Displays the bitrate for cloud audio transmission. This data metric is less likely to be affected by network conditions or performance.
Common Issues and Self-help Troubleshooting Methods
Users report severe lag during use. How should this be handled?
It is recommended to obtain the RequestId of this session from the backend data, and query the RTT, GPU usage rate, CPU usage rate, memory, and frame rate for that time period on the session status query page. Possible reasons for the lag include:
1. If the RTT is high, it can be determined that the user's poor network conditions are causing the screen to lag, along with a degree of packet loss leading to blurred images and dropped frames.
2. If the FPS is low, it can be determined that the issue is caused by the cloud machine's rendering results. You can check the GPU/CPU/memory usage rate to see whether there is a performance bottleneck, and it could also be due to the application itself.
Users report the screen goes black. How should this be handled?
First, based on the RequestId and the connection results of this session, determine whether a connection to CAR has been established. Sometimes, a black screen occurs because preliminary steps were not executed successfully, and the process has not progressed to connecting to the cloud display. If CAR has been connected, query the RTT, GPU usage rate, CPU usage rate, memory, frame rate, and downlink bitrate for that time period on the session status query page. Possible reasons for black screens include:
1. If the frame rate and bitrate are both 0, it can be determined that CAR has disconnected from the client. It is necessary to check the logs to see whether the session was terminated, and whether there was a reconnection logic in the code if the network instability led to disconnection.
2. If the frame rate and bitrate are not 0, it indicates that CAR is still connected. A black screen might be due to the application loading/starting, or because the application has frozen or crashed. The analysis should be done in conjunction with the GPU usage rate, CPU usage rate, and memory data, as well as application logs. Refer to Value-Added Features (Saving Application Logs and Archives) for methods to obtain cloud logs.
Users report blurred application images. How should this be handled?
First, obtain the RequestId of this session from the backend data, and query the RTT, frame rate, and video downlink bitrate for that time period on the session status query page. Possible reasons for blurred images include:
1. If the RTT is high and the downlink bitrate is unstable, it can be determined that the user's poor network conditions are causing the screen to lag, along with a degree of packet loss leading to blurred images and dropped frames.
2. If the downlink bitrate remains at a very low level, it is necessary to check the bitrate range settings in the project configuration. If the bitrate is set within a very low range (for example, below 3 Mbps), blurred images and mosaic effects are likely to occur in 3D scenes and complex images.
Yes
No
Was this page helpful?