20240829

I feel hot. I'm not sure if it's because I ran a long distance today or because the temperature in my room is actually high.

I wanted to do push-ups, but my wrists hurt. I will buy wrist wraps to reduce the damage of push-ups exercise.

Checked docker stats in my Mastodon instance

My mastodon server sometimes go down due to CPU burst.

I haven't configured logs, and also Amazon Lightsail is not very stable, so I have no idea what were the root causes of server down. I only know that there were CPU bursts by checking the Lightsail dashboard.

$ docker stats --no-stream
CONTAINER ID   NAME        CPU %     MEM USAGE / LIMIT     MEM %     NET I/O           BLOCK I/O        PIDS
dc2caa0b2959   nginx       0.02%     6.012MiB / 1.876GiB   0.31%     669MB / 372MB     208MB / 130MB    3
4fbcab03a3a0   sidekiq     0.21%     334.8MiB / 1.876GiB   17.43%    2.96GB / 2.69GB   2.32GB / 767MB   21
611a9610cbad   streaming   0.74%     43.02MiB / 1.876GiB   2.24%     1.64MB / 1.62MB   399MB / 0B       15
82d8a11a5237   web         0.09%     612.3MiB / 1.876GiB   31.87%    1.23GB / 889MB    309MB / 23MB     34
2446e58e07c1   db          0.00%     187.4MiB / 1.876GiB   9.75%     347MB / 1.58GB    2.14GB / 3.6GB   14
ccc445672682   redis       0.27%     8.898MiB / 1.876GiB   0.46%     1.01GB / 617MB    279MB / 4.99GB   6

I'm using Amazon Lightsail VPS, and its sustainable CPU usage is 20% of max. As I checked the CPU usage, it seems not to be a problem.

My guesstimate is that the server runs out of memory (why?), resulting high CPU usage.

The issue happens even if I don't open the Mastodon website, i.e., the main API backend is not processing heavily.

Maybe the processes to accept requests from other instances and process them in the background get too many requests and go burst.

I'm not sure.


Rice 400 Mexican rice 500 Protein shake 200 Salad 500 Honey 100 Yogurt 200

Total 1900 kcal

6k run


MUST:

TODO:


index 20240828 20240830