User avatar
ava@soon39c3:~cursor_blinkingverifiedlesbian @star@amazonawaws.com
2mo
@theking This is the resource consumption spike that this very response you just made triggered:
columns from left to right are: CONTAINER ID, NAME, CPU percentage, MEM USAGE divided by LIMIT, MEM percentage, NET I/O, BLOCK I/O, and PIDS. The first container e58c1daec2c5 named iceshrimp.net_web shows high CPU usage at 222.68% in yellow text, using 342.8MiB out of 9.711GiB memory at 3.45%, network traffic of 45.6MB received and 32.5MB sent, block I/O of 55MB read and 0B written, with 40 process IDs. The second container 6e32ce9ef842 named nextcloud-app-1 shows 0.02% CPU, 297.9MiB memory usage at 3.00%, 1.16GB received and 97.2MB sent network traffic, 84.1GB read and 1.89GB written block I/O, with 14 PIDs. The third container 8db63c3fd47 named immich_server uses 0.23% CPU, 812.3MiB memory at 8.17%, 32.9MB network I/O in both directions, 204MB read and 1.67GB written block I/O, with 32 PIDs. The fourth container 8281ba2e409f named immich_machine_learning uses 0.45% CPU, 393.4MiB memory at 3.96%, 293MB received and 15.4MB sent network traffic, 79.7GB read and 781MB written block I/O, with 19 PIDs. The fifth container 90cf2440d212 named iceshrimp.net_db shows elevated CPU at 171.27% in yellow text, 146.1MiB memory at 1.47%, 469MB received and 730MB sent network traffic, 77.7GB read and 1.96GB written block I/O, with 24 PIDs.