<?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: Patriot Ignite SSD Review (480GB) &#8211; Async Flash Takes On a Whole New Look	</title>
	<atom:link href="https://www.thessdreview.com/our-reviews/patriot-ignite-ssd-review-480gb-asynch-flash-takes-whole-new-look/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.thessdreview.com/our-reviews/patriot-ignite-ssd-review-480gb-asynch-flash-takes-whole-new-look/</link>
	<description>The Worlds Dedicated SSD Education and Review Resource &#124;</description>
	<lastBuildDate>Mon, 17 Aug 2015 19:48:00 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Lsi		</title>
		<link>https://www.thessdreview.com/our-reviews/patriot-ignite-ssd-review-480gb-asynch-flash-takes-whole-new-look/#comment-22172</link>

		<dc:creator><![CDATA[Lsi]]></dc:creator>
		<pubDate>Mon, 17 Aug 2015 19:48:00 +0000</pubDate>
		<guid isPermaLink="false">https://www.thessdreview.com/?p=85335#comment-22172</guid>

					<description><![CDATA[I wouldn&#039;t agree with the reviewer&#039;s statements about async NAND causing the lower bandwidth in the PCMark recovery phases, as its latency didn&#039;t rebound properly either.

Async NAND normally has reduced peak read bandwidth vs sync, but in this case the Phison controller&#039;s parallel channel operations or some form of interleaving along with those features avoid this as seen in the AS-SSD tests which can&#039;t be fooled by the controller&#039;s data compression acceleration.

The reduced bandwidth and increased latency in the recovery stages is most likely either a marginal TRIM implementation or a very lazy one to avoid big stutters / latency from the drive doing garbage collection, which instead appears to cause longer-term performance degradation.  Since we never seen those numbers properly settle like the other drives, how long the TRIM process takes to fully complete is unknown.  TRIM is drive-controlled vs OS controlled--the OS simply passes the command (if supported) and then the drive is on its own to do the TRIM processing at its leisure.  In this case it seems like the drive&#039;s firmware performs TRIM very slowly as a background process, which affects both drive response and peak bandwidth (despite it being a quad core controller).

Unfortunately Patriot is very bad for releasing SSD firmware updates in a timely matter (if at all).  Despite the impressive ability of the Phison S10 controller to minimize the compromises of async vs sync flash, I&#039;d buy this architecture from another manufacturer if another product comes along at a similar price until Patriot proves itself to be taking the SSD market seriously again.  A classic example of Patriot&#039;s behavior is that 3+ years later, the finally released firmware beyond the TRIM-broken 5.02 firmware (TRIM-fixed 5.04 was released and then pulled) for their Pyro Sandforce based drives a few months back.  This is YEARS too late, and their site only provides a download for their Pyro drives; their other (higher end) Sandforce-based drives which should use the identical firmware release (Pyro SE and Wildfire) are no longer even listed in the downloads section.  Apparently even spending a premium for Patriot&#039;s higher end offerings means nothing to them, so I&#039;ve basically blacklisted using them for any of my work until they prove themselves worthy of anything more than a plug-n-run-away install.

Silicon Power produces drives with Phison controllers (albeit randomly interchanged with SF-based drives under the same product name), and they have a much better track record for supporting them with firmware updates.  If they produced a similar S10-based drive, that would be my recommendation.]]></description>
			<content:encoded><![CDATA[<p>I wouldn&#8217;t agree with the reviewer&#8217;s statements about async NAND causing the lower bandwidth in the PCMark recovery phases, as its latency didn&#8217;t rebound properly either.</p>
<p>Async NAND normally has reduced peak read bandwidth vs sync, but in this case the Phison controller&#8217;s parallel channel operations or some form of interleaving along with those features avoid this as seen in the AS-SSD tests which can&#8217;t be fooled by the controller&#8217;s data compression acceleration.</p>
<p>The reduced bandwidth and increased latency in the recovery stages is most likely either a marginal TRIM implementation or a very lazy one to avoid big stutters / latency from the drive doing garbage collection, which instead appears to cause longer-term performance degradation.  Since we never seen those numbers properly settle like the other drives, how long the TRIM process takes to fully complete is unknown.  TRIM is drive-controlled vs OS controlled&#8211;the OS simply passes the command (if supported) and then the drive is on its own to do the TRIM processing at its leisure.  In this case it seems like the drive&#8217;s firmware performs TRIM very slowly as a background process, which affects both drive response and peak bandwidth (despite it being a quad core controller).</p>
<p>Unfortunately Patriot is very bad for releasing SSD firmware updates in a timely matter (if at all).  Despite the impressive ability of the Phison S10 controller to minimize the compromises of async vs sync flash, I&#8217;d buy this architecture from another manufacturer if another product comes along at a similar price until Patriot proves itself to be taking the SSD market seriously again.  A classic example of Patriot&#8217;s behavior is that 3+ years later, the finally released firmware beyond the TRIM-broken 5.02 firmware (TRIM-fixed 5.04 was released and then pulled) for their Pyro Sandforce based drives a few months back.  This is YEARS too late, and their site only provides a download for their Pyro drives; their other (higher end) Sandforce-based drives which should use the identical firmware release (Pyro SE and Wildfire) are no longer even listed in the downloads section.  Apparently even spending a premium for Patriot&#8217;s higher end offerings means nothing to them, so I&#8217;ve basically blacklisted using them for any of my work until they prove themselves worthy of anything more than a plug-n-run-away install.</p>
<p>Silicon Power produces drives with Phison controllers (albeit randomly interchanged with SF-based drives under the same product name), and they have a much better track record for supporting them with firmware updates.  If they produced a similar S10-based drive, that would be my recommendation.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Babel 17		</title>
		<link>https://www.thessdreview.com/our-reviews/patriot-ignite-ssd-review-480gb-asynch-flash-takes-whole-new-look/#comment-21741</link>

		<dc:creator><![CDATA[Babel 17]]></dc:creator>
		<pubDate>Thu, 14 May 2015 13:52:00 +0000</pubDate>
		<guid isPermaLink="false">https://www.thessdreview.com/?p=85335#comment-21741</guid>

					<description><![CDATA[Good article, but I just noticed what I think is a typo from your spell checker.
&quot;Alas, the Ignite also contains many error correcting features along with
 end-to-end data path protection to aid in data reliability, and it does
 have AES 256-bit encryption to top that off, unlike many others.&quot;
From the context, I&#039;d guess you meant &quot;Also&quot; instead of &quot;Alas&quot;. &quot;Alas&quot; implies regret, disappointment, sadness, and so on.]]></description>
			<content:encoded><![CDATA[<p>Good article, but I just noticed what I think is a typo from your spell checker.<br />
&#8220;Alas, the Ignite also contains many error correcting features along with<br />
 end-to-end data path protection to aid in data reliability, and it does<br />
 have AES 256-bit encryption to top that off, unlike many others.&#8221;<br />
From the context, I&#8217;d guess you meant &#8220;Also&#8221; instead of &#8220;Alas&#8221;. &#8220;Alas&#8221; implies regret, disappointment, sadness, and so on.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
