[Raspberry Pi 4B Review] + Real-time status monitoring website test service resource usage
[Copy link]
This post was last edited by sylar^z on 2020-9-22 20:23
In the previous evaluation, I have built XRDP remote desktop service, DLNA , FTP , ARIA2 and real-time status monitoring website service in Raspberry Pi. Now I just use the real-time status monitoring website to test the usage of system resources by the above service functions.
First, it is a real-time status monitoring website, recorded in percentage (the same below). This occupies about 10+ resources , jumps to 30+ every few seconds, and jumps to 34 at the highest . The memory usage is 1174M , which is relatively large because I downloaded the file before the demonstration.
In the second video, I turned off aria2 , ftp , and dlna at startup, and after restarting, the resource usage and CPU usage were basically the same as when they were turned on, and the memory was about 300M .
Next is the FTP function. When testing downloading movies from the Raspberry Pi's FTP , the transfer speed is 2M+ , as can be seen from the WLAN0 data transfer rate icon below . At this time, the CPU usage increased by about 10 , reaching 20+ . There was no obvious change in memory.
The second video is uploading a video to the Raspberry Pi, with a transmission speed of 2M+ . At this time, the CPU usage reaches 30+/40+ . The memory does not change significantly. The memory continues to increase with the upload, and the downloaded file will be stored in the memory.
Next is the ARIA2 function. When testing the Raspberry Pi to download the software package from the Internet, the transmission speed is 3M+ , which can also be seen from the WLAN0 data transmission rate icon below . At this time, the CPU usage probably increased a lot, reaching 50+/70+ . The memory continues to increase as the download, and the downloaded files will be stored in the memory. After the upload is completed, the memory usage is greater than the actual memory plus the file size ( 500M ). And after I logged out of the FTP connection, the memory did not decrease.
Next is the DLNA service. The test phone plays the movie on the Raspberry Pi through the DLNA service. The phone starts playing the cached data from about 8 seconds, and the data transmission is between 1M and 2.5M . At this time, the CPU usage has increased by less than 10 , and there is no obvious change in memory.
Next is the XRDP remote desktop service. Test the PC remote connection to the Raspberry Pi desktop. The CPU usage is relatively high during the connection verification, above 56 , and up to 98. After the verification is completed, the CPU usage begins to drop to around 40 when the desktop is transferred . During regular remote operation, the CPU usage is almost the same as during five remote operations. After that, I transferred the remote desktop to the extended display to continue the operation. When opening folders, terminals, and software, the CPU usage will increase significantly. When operating folders and terminals normally, the CPU usage will change significantly. When the main screen changes greatly, the data transmission volume increases, and the CPU usage rate increases slightly. The memory did not change much during this period. In general, this remote software does not have a high CPU usage rate and does not require much memory, so it is relatively easy to use.
In general, the Raspberry Pi has no problem with the above applications and is very suitable. The Raspberry Pi's reading, storage and output functions do not occupy much CPU and memory resources. Writing to the Raspberry Pi storage requires write operations and cache, which occupies a lot of resources for both, especially high-speed downloads. This may also be related to the performance of the SD card .
Another point is that the data cached in the memory during downloading occupies a lot of space. When I close the corresponding function link, such as ARIA2 connection, the cache in the memory still exists and does not decrease, which will affect the user experience.
|