Curious what other’s thoughts on this are. currently by default the boot-pool does not have the autotrim property enabled which could be detrimental to SSD health. there also doesn’t seem to be a way to enable autotrim from the webui as far as I can tell.
I have had autotrim enabled on my boot-pool and manually trimmed a few times since… dragonfish..? I can’t think of a reason why it would be harmful to enable it (outside of outright broken hardware).
It would be nice if the setting for enabling autotrim was there for the boot pool. Normal pools have an option to toggle this in the UI, but it’s not there in the boot pool settings.
I just spent an hour trying to debug why I’m getting abysmal performance on my boot pool (updates were taking several minutes to decompress), until I checked the pool properties. On my system autotrim seems to be required, most likely because I’m running a 10 year old 64GB SATADOM, but still, an option in the UI would be nice.
Issues arounf stuff breaking is discussed here in the T3 podcast:
Has there been an option put into v27 for this?
This is absolutely needed here is are some reasons:
I am running truenas on virtualbox with a dynamic disk and with all of the different truenas version i have installed my boot disk has got large. To reduce it I need the space in the drive to be marked as empty before I can run the compacting routine in virtualbox.
If space is never marked as empty, data is pushed further towards the end of the drive, and with SSDs this affects performance because instead of just using level one for data storage they are then push to using 2nd and 3rd layer stacking on the sane cell leading to extra processing being done and thus a performance degradation.