<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Performance, too:</div><div><p></p><blockquote type="cite">from <a href="http://www.eetimes.com/document.asp?doc_id=1328682">http://www.eetimes.com/document.asp?doc_id=1328682</a></blockquote><blockquote type="cite"><span style="background-color: rgba(255, 255, 255, 0);">"In an NVMe-based solid state drive, XPoint chips can deliver more than 95,000 I/O operations per second at a 9 microsecond latency, compared to 13,400 IOPs and 73 ms latency for flash."</span></blockquote><p></p><div><br></div><div>Sent from my iPhone</div></div><div><br>On Feb 9, 2016, at 16:47, Craig Cruden via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8">Much sooner…… Optane (which should dramatically increase the durability) is out this year from Intel, and the competitors plan to have equivalent out in a year I think…. <div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 2016-02-10, at 7:43:40, Goffredo Marocchi via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><div class="">I think those changes can be overcome... but yes, it is not something that would happen tomorrow... More like five years from now ;). *Crossing fingers for memristors or some new nonvolatile storage solution to overcome the current flash issue with frequent read/write cycles....*</div><div class=""><br class=""></div><div class="">Maybe enough redundancy and better controllers can allow the same flexibility on mobile's that we enjoy on any SSD on laptops and desktops nowadays and similar I/O throughout though. <br class=""><br class="">Sent from my iPhone</div><div class=""><br class="">On 10 Feb 2016, at 00:32, Greg Parker <<a href="mailto:gparker@apple.com" class="">gparker@apple.com</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div class="">On Feb 9, 2016, at 2:21 PM, Goffredo Marocchi via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><div class=""><div dir="auto" class=""><div class=""><br class=""></div><div class=""><blockquote type="cite" class="">On 9 Feb 2016, at 18:18, Charles Srstka via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""></blockquote><blockquote type="cite" class=""><br class=""></blockquote></div><blockquote type="cite" class=""><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><blockquote type="cite" class="">On Feb 9, 2016, at 8:35 AM, Jean-Denis Muys via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""></blockquote><div class=""><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><blockquote type="cite" class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span class="" style="color: rgb(35, 31, 32); font-family: 'Open Sans', sans-serif; font-size: 13.888888359069824px; background-color: rgb(255, 255, 255);">It’s a long since resolved dispute, and GC won. I don’t want Steve Jobs to reach out from the grave and drag us back to the 70s. There’s nothing special about mobile phones: they are more powerful than the computers that GC won on in the first place.</span></blockquote></div></blockquote></div><br class=""><div class="">I’d disagree with that, for one rather important reason; the computers that GC won on had virtual memory. On mobile, when your RAM runs out, it’s out. So RAM constraints are somewhat more serious on mobile.</div></div></blockquote></div></div></blockquote><div class=""><blockquote type="cite" class=""><br class=""></blockquote></div><blockquote type="cite" class="">This will be then more fun when we have page file support as virtual memory is already there.<br class=""></blockquote></div><div class=""><br class=""></div>Unlikely with current hardware technology. NAND storage on mobile devices has limited lifetime based on the number of writes. Adding a swap file would burn through that lifetime awfully fast.<br class=""><br class=""><div class=""><br class=""></div><div class="">-- </div><div class="">Greg Parker <a href="mailto:gparker@apple.com" class="">gparker@apple.com</a> Runtime Wrangler</div><div class=""><br class=""></div><div class=""><br class=""></div></div></blockquote></div>_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""></div></blockquote></div><br class=""></div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></body></html>