-
Notifications
You must be signed in to change notification settings - Fork 190
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
When running in an hypervisor with SSD disks, detection is not accurate. #41
Comments
Hi guetti, |
@PitoneMaledetto I know the |
@guettli , benching disk would be too agressive, it could have a perfomance impact on a production database and/or report bad values due to parallel database activity. The design of this script was made to be non-agressive to the server performances. |
Why not let the user decide? You could provide a autodetect-ssd flag and a server-has-ssd flag. Then the user can decide what he wants. There are arguments for both ways. Then everyone would be happy. |
When scanning for "rotational" flag you filter out special directories ("." and "..") and "^sr" devices. It makes sense to add a filter for "^loop" devices as well. Those are pseudo devices. |
Devices can have different names. Is it possible to measure the performance of the drive? This is the value which is all about. After measuring the performance the matching config value can get calculated. |
Where do you draw the line? Imagine your VM running on a storage with spinning rust and half a TB of cache - are you planning to write a ton of data so a really large cache fills up? Really, detection of SSDs is unreliable when it's hidden behind a virtualization layer. |
@realulli Why not check the performance of the disk and set the values according the this value (float value, not boolean)? |
I read this in the README:
I guess you are trying to detect if there are SSD disks and then you have a boolean flag.
Why do you do it this way?
Why not check the performance of the disk and set the values according the this value (float value, not boolean)?
The text was updated successfully, but these errors were encountered: