<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Trimming SSD Performance Degradation	</title>
	<atom:link href="https://www.thessdreview.com/ssd-guides/optimization-guides/ssd-performance-loss-and-its-solution/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.thessdreview.com/ssd-guides/optimization-guides/ssd-performance-loss-and-its-solution/</link>
	<description>The Worlds Dedicated SSD Education and Review Resource &#124;</description>
	<lastBuildDate>Mon, 18 Nov 2013 13:02:00 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Alan		</title>
		<link>https://www.thessdreview.com/ssd-guides/optimization-guides/ssd-performance-loss-and-its-solution/#comment-16670</link>

		<dc:creator><![CDATA[Alan]]></dc:creator>
		<pubDate>Mon, 18 Nov 2013 13:02:00 +0000</pubDate>
		<guid isPermaLink="false">https://thessdreview.com/?p=3253#comment-16670</guid>

					<description><![CDATA[Hi Les,
I understand the concept and value of overprovisioning but not how best to implement it.  Some writers say it is enough to just leave empty space on the drive in the same partition as the OS whilst others say it is necessary to make an unallocated partition which will then be used by the controller as overprovisioned space. I wonder if you could clarify this. I am using OCZ Vectors.]]></description>
			<content:encoded><![CDATA[<p>Hi Les,<br />
I understand the concept and value of overprovisioning but not how best to implement it.  Some writers say it is enough to just leave empty space on the drive in the same partition as the OS whilst others say it is necessary to make an unallocated partition which will then be used by the controller as overprovisioned space. I wonder if you could clarify this. I am using OCZ Vectors.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Les@TheSSDReview		</title>
		<link>https://www.thessdreview.com/ssd-guides/optimization-guides/ssd-performance-loss-and-its-solution/#comment-16667</link>

		<dc:creator><![CDATA[Les@TheSSDReview]]></dc:creator>
		<pubDate>Sun, 17 Nov 2013 19:40:00 +0000</pubDate>
		<guid isPermaLink="false">https://thessdreview.com/?p=3253#comment-16667</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.thessdreview.com/ssd-guides/optimization-guides/ssd-performance-loss-and-its-solution/#comment-16666&quot;&gt;jameskatt&lt;/a&gt;.

Unfortunately I am not an expert, nor would I jump at that designation for many in this industry but you answer your question right off when you spoke of garbage collection in SF drives.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.thessdreview.com/ssd-guides/optimization-guides/ssd-performance-loss-and-its-solution/#comment-16666">jameskatt</a>.</p>
<p>Unfortunately I am not an expert, nor would I jump at that designation for many in this industry but you answer your question right off when you spoke of garbage collection in SF drives.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: jameskatt		</title>
		<link>https://www.thessdreview.com/ssd-guides/optimization-guides/ssd-performance-loss-and-its-solution/#comment-16666</link>

		<dc:creator><![CDATA[jameskatt]]></dc:creator>
		<pubDate>Sun, 17 Nov 2013 19:27:00 +0000</pubDate>
		<guid isPermaLink="false">https://thessdreview.com/?p=3253#comment-16666</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.thessdreview.com/ssd-guides/optimization-guides/ssd-performance-loss-and-its-solution/#comment-16665&quot;&gt;Les@TheSSDReview&lt;/a&gt;.

Since SSDs sooner or later are going to take over Rotational Hard Drives for external USB 3.0 general purpose storage, it should be true that TRIM is no longer needed.  USB 3.0 drives will not receive TRIM commands even if TRIM is enabled.


Since you test SSDs on this site, I think you would be most expert in determining if SSDs installed in external USB 3.0 enclosures have performance degradation over time since they won&#039;t be capable of receiving the TRIM command.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.thessdreview.com/ssd-guides/optimization-guides/ssd-performance-loss-and-its-solution/#comment-16665">Les@TheSSDReview</a>.</p>
<p>Since SSDs sooner or later are going to take over Rotational Hard Drives for external USB 3.0 general purpose storage, it should be true that TRIM is no longer needed.  USB 3.0 drives will not receive TRIM commands even if TRIM is enabled.</p>
<p>Since you test SSDs on this site, I think you would be most expert in determining if SSDs installed in external USB 3.0 enclosures have performance degradation over time since they won&#8217;t be capable of receiving the TRIM command.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Les@TheSSDReview		</title>
		<link>https://www.thessdreview.com/ssd-guides/optimization-guides/ssd-performance-loss-and-its-solution/#comment-16665</link>

		<dc:creator><![CDATA[Les@TheSSDReview]]></dc:creator>
		<pubDate>Sun, 17 Nov 2013 19:21:00 +0000</pubDate>
		<guid isPermaLink="false">https://thessdreview.com/?p=3253#comment-16665</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.thessdreview.com/ssd-guides/optimization-guides/ssd-performance-loss-and-its-solution/#comment-16664&quot;&gt;jameskatt&lt;/a&gt;.

Although a dated article, the argument is a valid one, however, is primarily based on LSI SandForce controlled SSDs in this argument.  Can your same opinions be reflected for all manufacture of SSDs today?]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.thessdreview.com/ssd-guides/optimization-guides/ssd-performance-loss-and-its-solution/#comment-16664">jameskatt</a>.</p>
<p>Although a dated article, the argument is a valid one, however, is primarily based on LSI SandForce controlled SSDs in this argument.  Can your same opinions be reflected for all manufacture of SSDs today?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: jameskatt		</title>
		<link>https://www.thessdreview.com/ssd-guides/optimization-guides/ssd-performance-loss-and-its-solution/#comment-16664</link>

		<dc:creator><![CDATA[jameskatt]]></dc:creator>
		<pubDate>Sun, 17 Nov 2013 19:05:00 +0000</pubDate>
		<guid isPermaLink="false">https://thessdreview.com/?p=3253#comment-16664</guid>

					<description><![CDATA[The biggest argument I have against enabling TRIM is that TRIM is a SATA-only command.

SSDs attached via PCIe, USB 3.0, FireWire, or Thunderbolt cannot receive the TRIM command.  Macs won&#039;t even recognize them as SSDs nor would the Mac send them the TRIM command even if it is enabled.

The newest MacBooks now use PCIe SSDs. 

SSDs (such as OWC Mercury SSDs with SandForce controllers) have evolved to the point they don&#039;t need TRIM - particularly when the SSDs are not attached via SATA?  They do their own garbage-collection and optimization. 

OWC - in particular - advises against enabling TRIM on their Sandforce controller OWC Mercury SSDs since this increases wear and tear on their SSDs. TRIM adds extra unnecessary writes when the SSD already did this on its own.  Enabling TRIM would essentially harm the SSD and shorten its lifespan. https://blog.macsales.com/11051-to-trim-or-not-to-trim-owc-has-the-answer

If modern SSDs need TRIM, they would be in danger of serious performance problems if the SSD was attached via a non-SATA connection such as USB 3.0 or PCIe or Firewire or Thunderbolt.  Unless the manufacturer insures their SSD&#039;s controller does its own version of TRIM, then they would suffer serious performance problems when attached via non-SATA connection compared to the competition.

This is why I argue that TRIM is currently useless in modern SSDs.]]></description>
			<content:encoded><![CDATA[<p>The biggest argument I have against enabling TRIM is that TRIM is a SATA-only command.</p>
<p>SSDs attached via PCIe, USB 3.0, FireWire, or Thunderbolt cannot receive the TRIM command.  Macs won&#8217;t even recognize them as SSDs nor would the Mac send them the TRIM command even if it is enabled.</p>
<p>The newest MacBooks now use PCIe SSDs. </p>
<p>SSDs (such as OWC Mercury SSDs with SandForce controllers) have evolved to the point they don&#8217;t need TRIM &#8211; particularly when the SSDs are not attached via SATA?  They do their own garbage-collection and optimization. </p>
<p>OWC &#8211; in particular &#8211; advises against enabling TRIM on their Sandforce controller OWC Mercury SSDs since this increases wear and tear on their SSDs. TRIM adds extra unnecessary writes when the SSD already did this on its own.  Enabling TRIM would essentially harm the SSD and shorten its lifespan. <a href="https://blog.macsales.com/11051-to-trim-or-not-to-trim-owc-has-the-answer" rel="nofollow ugc">https://blog.macsales.com/11051-to-trim-or-not-to-trim-owc-has-the-answer</a></p>
<p>If modern SSDs need TRIM, they would be in danger of serious performance problems if the SSD was attached via a non-SATA connection such as USB 3.0 or PCIe or Firewire or Thunderbolt.  Unless the manufacturer insures their SSD&#8217;s controller does its own version of TRIM, then they would suffer serious performance problems when attached via non-SATA connection compared to the competition.</p>
<p>This is why I argue that TRIM is currently useless in modern SSDs.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
