improve shred performance #44

Closed
opened 2022-08-04 20:19:14 +02:00 by localhorst · 4 comments
Owner

possible bottlenecks:

  • write chunks size not efficent
  • read from /dev/urandom is locking threads
possible bottlenecks: - write chunks size not efficent - read from /dev/urandom is locking threads
localhorst added the
bug
label 2022-08-04 20:19:14 +02:00
Author
Owner

implement Maximum-Performance-Tracker for write chunk size

implement Maximum-Performance-Tracker for write chunk size
Author
Owner

testruns:

  • urandom vs. memset
testruns: - urandom vs. memset
Author
Owner

calling a read from urandom is too slow. Using Threefish cipher based raw PRN/noise generator

calling a read from urandom is too slow. Using [Threefish cipher based raw PRN/noise generator](https://git.mosad.xyz/localhorst/tfnoisegen)
Author
Owner

closed with #46

closed with https://git.mosad.xyz/localhorst/reHDD/pulls/46
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: localhorst/reHDD#44
No description provided.