Jump to content

Raise Chunk/Block Size of Parity Calculation

Recommended Posts

Depending on the performance of the HDD and position of the data on the plattern, the writing speed of the parity varies:







I think the write speed could be better by raising the chunk/block size, so the amount of re-positionings of the Read-Write-Head is reduced. What is the actual size? Did the Limeteach developers already tested a bigger size?


Link to comment
  • 3 weeks later...

I’m not very sure on how this works, but by increasing blocksize would that not also mitigate some of the SMR-issues 


based on what i know,  with smr a track will be destroyed if the adjacent track is written and thus has to be re-written. 

This kind of is why smr is stil oké for linear writes but not for random writes.  


I would feel that file-system and parity calculation tuning. MAY somewhat mitigate the smr-drawback


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.

Reply to this topic...

×   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.

  • Create New...