<?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: SNIA &#038; Plexistor Demonstrate DDR4 NVDIMM &#8211; Storage Visions 2016 Update	</title>
	<atom:link href="https://www.thessdreview.com/ces-2016/snia-plexistor-demonstrate-nvdimm-storage-visions-2016-update/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.thessdreview.com/ces-2016/snia-plexistor-demonstrate-nvdimm-storage-visions-2016-update/</link>
	<description>The Worlds Dedicated SSD Education and Review Resource &#124;</description>
	<lastBuildDate>Tue, 05 Jan 2016 19:38:00 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Amit Golander		</title>
		<link>https://www.thessdreview.com/ces-2016/snia-plexistor-demonstrate-nvdimm-storage-visions-2016-update/#comment-22790</link>

		<dc:creator><![CDATA[Amit Golander]]></dc:creator>
		<pubDate>Tue, 05 Jan 2016 19:38:00 +0000</pubDate>
		<guid isPermaLink="false">https://www.thessdreview.com/?p=90645#comment-22790</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.thessdreview.com/ces-2016/snia-plexistor-demonstrate-nvdimm-storage-visions-2016-update/#comment-22788&quot;&gt;Dan&lt;/a&gt;.

SmartM configured the server with an Intel 750 NVMe, but the specific test shown in the article (out of five in the demo) is a single thread test. There is another multi-threaded test that reaches higher ops/sec.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.thessdreview.com/ces-2016/snia-plexistor-demonstrate-nvdimm-storage-visions-2016-update/#comment-22788">Dan</a>.</p>
<p>SmartM configured the server with an Intel 750 NVMe, but the specific test shown in the article (out of five in the demo) is a single thread test. There is another multi-threaded test that reaches higher ops/sec.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Dan		</title>
		<link>https://www.thessdreview.com/ces-2016/snia-plexistor-demonstrate-nvdimm-storage-visions-2016-update/#comment-22789</link>

		<dc:creator><![CDATA[Dan]]></dc:creator>
		<pubDate>Tue, 05 Jan 2016 18:36:00 +0000</pubDate>
		<guid isPermaLink="false">https://www.thessdreview.com/?p=90645#comment-22789</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.thessdreview.com/ces-2016/snia-plexistor-demonstrate-nvdimm-storage-visions-2016-update/#comment-22782&quot;&gt;Chris Jolliffe&lt;/a&gt;.

One small typo- 
Supercar -&#062; Supercap]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.thessdreview.com/ces-2016/snia-plexistor-demonstrate-nvdimm-storage-visions-2016-update/#comment-22782">Chris Jolliffe</a>.</p>
<p>One small typo-<br />
Supercar -&gt; Supercap</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Dan		</title>
		<link>https://www.thessdreview.com/ces-2016/snia-plexistor-demonstrate-nvdimm-storage-visions-2016-update/#comment-22788</link>

		<dc:creator><![CDATA[Dan]]></dc:creator>
		<pubDate>Tue, 05 Jan 2016 18:35:00 +0000</pubDate>
		<guid isPermaLink="false">https://www.thessdreview.com/?p=90645#comment-22788</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.thessdreview.com/ces-2016/snia-plexistor-demonstrate-nvdimm-storage-visions-2016-update/#comment-22781&quot;&gt;Amit Golander&lt;/a&gt;.

Which NVMe are you using?]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.thessdreview.com/ces-2016/snia-plexistor-demonstrate-nvdimm-storage-visions-2016-update/#comment-22781">Amit Golander</a>.</p>
<p>Which NVMe are you using?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Chris Jolliffe		</title>
		<link>https://www.thessdreview.com/ces-2016/snia-plexistor-demonstrate-nvdimm-storage-visions-2016-update/#comment-22782</link>

		<dc:creator><![CDATA[Chris Jolliffe]]></dc:creator>
		<pubDate>Mon, 04 Jan 2016 21:04:00 +0000</pubDate>
		<guid isPermaLink="false">https://www.thessdreview.com/?p=90645#comment-22782</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.thessdreview.com/ces-2016/snia-plexistor-demonstrate-nvdimm-storage-visions-2016-update/#comment-22781&quot;&gt;Amit Golander&lt;/a&gt;.

Hi, we appreciate the read and the comments, some corrections have been made.
We understand latency can never be zero, we are just going off of how the benchmark reads.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.thessdreview.com/ces-2016/snia-plexistor-demonstrate-nvdimm-storage-visions-2016-update/#comment-22781">Amit Golander</a>.</p>
<p>Hi, we appreciate the read and the comments, some corrections have been made.<br />
We understand latency can never be zero, we are just going off of how the benchmark reads.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Amit Golander		</title>
		<link>https://www.thessdreview.com/ces-2016/snia-plexistor-demonstrate-nvdimm-storage-visions-2016-update/#comment-22781</link>

		<dc:creator><![CDATA[Amit Golander]]></dc:creator>
		<pubDate>Mon, 04 Jan 2016 20:11:00 +0000</pubDate>
		<guid isPermaLink="false">https://www.thessdreview.com/?p=90645#comment-22781</guid>

					<description><![CDATA[Few comments:
1. Plexistor software-defined memory (SDM) is software. The NVDIMM cards actually belong to SmartM in this demo
2. Plexistor SDM is multi-tiered, so it consumes both NVDIMM and FLASH NVMe resources 
3. Latency is never zero ;-)   it is 1-2 micro seconds for this bechmark]]></description>
			<content:encoded><![CDATA[<p>Few comments:<br />
1. Plexistor software-defined memory (SDM) is software. The NVDIMM cards actually belong to SmartM in this demo<br />
2. Plexistor SDM is multi-tiered, so it consumes both NVDIMM and FLASH NVMe resources<br />
3. Latency is never zero 😉   it is 1-2 micro seconds for this bechmark</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
