-
Notifications
You must be signed in to change notification settings - Fork 2
hw_disk_bus: scsi for kubernetes images #1
Comments
I'd be really hesitant to switch the default here and would like to see actual current numbers that scsi is more performant. as said elsewhere already: virtio-blk does support discard. |
So, i quickly re-researched the performance topic and so far I mostly found sources in favor of virtio-blk when it comes to performance:
:edit: this all being said, this research is really just a few minutes of googling around so it might be very well possible this information is outdated so I'd be interested in learning of newer sources that disprove the above. |
Please take to an SCS meeting an discuss there. |
@linwalth can you check if virtio-blk works for you in terms of discard? do you see any performance difference - positive or negative - for your workload? I don't know your platform/usecase, as I'm still a little new here around 😄 If you have a problem with the current value or if you can show data that scsi works better for your usecase, we could discuss switching this again. Thanks! |
@berendt I added the topic to the agenda, I hope it's okay this way: |
that link is kaput ;) Where did you add it? |
yeah, the markdownlinks are somehow defect, it's here (deeplinks seem to be broken somehow): |
@artificial-intelligence I was just passing this issue down, I have no immediate contact with the usecase itself. |
I have found through some digging that the use of virtio as hw_disk_bus is not needed anymore.
(see osism/openstack-image-manager#482)
so these parameters can be set to scsi (as scsi appears to be slightly more perfomant, allowing for DISCARD [fstrim].)
https://github.com/osism/openstack-image-manager/blob/main/etc/images/kubernetes.yml#L15
https://github.com/osism/openstack-image-manager/blob/main/etc/images/gardenlinux.yml#L14
The text was updated successfully, but these errors were encountered: