• slower parity check


    endystrike
    • Minor

    Hello everyone,

    just wanted to report that in 6.12.0-rc2 the speed of parity check seems to be slower than in 6.11.5 by ~10%.

    I always do parity check disabling all the dockers that could access file and all VM were shut down, turn off all user scripts may have access to the array and don't use any share on the Unraid server from any PC (I did parity check at night and all other PCs were shut down), so I'm sure 100% I did all parity checks you see here in the same conditions.

     

    image.thumb.png.d293287fa519bc799cf52f24a5f7da5c.png

     

    I attach diagnostic report, hoping it may help. :)

     

    endys-diagnostics-20230412-0149.zip




    User Feedback

    Recommended Comments

    I'm not seeing any difference, even for large 30 drive arrays, please try again with mitigations disabled, there are new kernel mitigations that can have a noticeable performance impact, and unless you are renting VM space on your server it should be pretty safe to run without them.

     

    image.png

     

     

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.