Follow

was struggling a bit

gonna monitor it

@subleq Was checking 5 mins before it recovered. High disk I/O, but no clue what was causing it. That block storage thing looks pretty slow. :ablobnervous:

@ayo i have suspicions that it's sidekiq's 25 threads but all i did was enable swap and stop elastic for a bit

@subleq Memory was fine though, 1G buffered and not swapping. Could be an (ES? Masto?) housekeeping action killing the disk.

@subleq But I guess reducing sidekiq's threads wouldn't hurt, those PG connections are using more memory than necessary.

@ayo it's settled down now, i'll modify sidekiq down

Sign in to participate in the conversation
lonely.town

A lonely little town in the wider world of the fediverse.