Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The InnoDB log buffer size recommendation may be tested too strictly #569

Closed
64kramsystem opened this issue Oct 15, 2021 · 1 comment
Closed

Comments

@64kramsystem
Copy link
Contributor

64kramsystem commented Oct 15, 2021

Currently, if there is any InnoDB log wait, the recommendation to increase the log buffer size is given.

The problem is that this is given even for cases where the the number of waits is extremely low:

[!!] InnoDB log waits: 0.00% (30 waits / 712207732 writes)

An amount like this is essentially noise under regular circumstances, so I think that the threshold should be increased, even if by a tiny amount.

The source code is:

    if ( defined $mystat{'Innodb_log_waits'}
        && $mystat{'Innodb_log_waits'} > 0 )
    {
        badprint "InnoDB log waits: "
          . percentage( $mystat{'Innodb_log_waits'},
            $mystat{'Innodb_log_writes'} )
          . "% ("
          . $mystat{'Innodb_log_waits'}
          . " waits / "
          . $mystat{'Innodb_log_writes'}
          . " writes)";
        push( @adjvars,
                "innodb_log_buffer_size (>= "
              . hr_bytes_rnd( $myvar{'innodb_log_buffer_size'} )
              . ")" );
    }

It's hard to give a threshold, but I think that even something very little as 0.000001 (1.0 / 10^6) is sensible:

    if ( defined $mystat{'Innodb_log_waits'}
        && (computed_log_waits_occurrence > 0.000001 )
@jmrenouard
Copy link
Collaborator

Fixed ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants