For users with solid state storage devices, TRIM can be used to inform the drive which storage blocks are no longer in use and can be wiped internally, thus preventing performance hits from spurious over-writes and write amplification.

I consider myself a fairly heavy user when it comes to modifying/deleting files by way of video editing, C programming, photo editing, web browsing, etc, and I've seen no perceivable performance change with or without the discard option. In fact, I'm happy to use neither discard nor fstrim, because the SSD's built-in garbage collection will do the job as it's needed. Crucial's SSDs will do garbage collection during idle periods, so it's unnoticeable.

Also, with modern SSD's, there is no need to be concerned with how full the drive is getting because there is enough over-provisioning of space for it to be a non-issue.

EDIT: Incidentally, I realise the thread is about TRIM but, is it worth mentioning noatime & nodiratime mount options?

phenest wrote:I'm happy to use neither discard nor fstrim, because the SSD's built-in garbage collection will do the job as it's needed. Crucial's SSDs will do garbage collection during idle periods, so it's unnoticeable.

Also, with modern SSD's, there is no need to be concerned with how full the drive is getting because there is enough over-provisioning of space for it to be a non-issue.

This is fair comment.

Slightly related: I have an SSD in my ThinkPad that runs OpenBSD and their filesystem offers no (userspace) TRIM options at all but the developers seem to suggest that any management is automagical and mostly at the hardware level: