News for hackers. Stuff that matters.
Re:What we learned about SSDs in 2015 by wtallis on Sunday December 20, 2015 @04:24PM (#10768352)
Take a look at how much stricter the temperature and airflow requirements are for Intel's 2.5" U.2 drives compared to their add-in card counterparts. (And note that the U.2 drives are twice as thick as most SATA drives.)

M.2 has almost no place in the server market. U.2 does and will for the foreseeable future, but I'm not sure that it can serve the high-performance segment for long. It's not clear whether it will reach the limits on capacity, heat, or link speed first, but all of those limits are clearly much closer than for add-in cards.

Re:What we learned about SSDs in 2015 by lsc on Sunday December 20, 2015 @05:37PM (#10768584)
>M.2 has almost no place in the server market. U.2 does and will for the foreseeable future, but I'm not sure that it can serve the high-performance segment for long. It's not clear whether it will reach the limits on capacity, heat, or link speed first, but all of those limits are clearly much closer than for add-in cards.

No argument on m.2 - it's a consumer grade technology. No doubt, someone in the "cloud" space will try it... I mean, if you rely on "ephemeral disk" - well, this is just "ephemeral disk" that goes funny sooner than spinning disk.

But the problem remains, If your servers aren't disposable, if your servers can't just go away at a moment's notice, the form factor of add-in cards is going to be a problem for you, unless the add-in cards are massively more reliable than I think they are. Taking down a whole server to replace a failed disk is a no-go on most non-cloud applications...

Re:What we learned about SSDs in 2015 by kijiki on Sunday December 20, 2015 @06:31PM (#10768774)
You're probably tired of hearing this from me, but if you distribute the storage, you can evacuate all the VMs off a host, down it, do whatever, bring it back up, and then unevacuate.
Re:What we learned about SSDs in 2015 by lsc on Sunday December 20, 2015 @08:56PM (#10769152)
> You're probably tired of hearing this from me, but if you distribute the storage, you can evacuate all the VMs off a host, down it, do whatever, bring it back up, and then unevacuate.

Yes. The same conversation is happening right now in the living room, because security has forced three reboots in the last year, after having several years where simply by being xen and pv and using pvgrub (rather than loading a user kernel from the dom0) we haven't been vulnerable to the known privilege escalations. This is a lot more labor (and customer pain) when you can't move people.

No progress on that front yet, though.

Re:What we learned about SSDs in 2015 by wtallis on Sunday December 20, 2015 @08:03PM (#10769012)
And if uptime is that important, you can just buy a server that supports PCIe hotswap.
Re:What we learned about SSDs in 2015 by lsc on Sunday December 20, 2015 @08:32PM (#10769093)
can you point me at a chassis designed for that?
Re:What we learned about SSDs in 2015 by wmf on Sunday December 20, 2015 @06:11PM (#10768700)
OTOH if you can fit 24 U.2s but only 6 AICs in a server, maybe RAIDed U.2 will still win.
Re:What we learned about SSDs in 2015 by wtallis on Sunday December 20, 2015 @07:58PM (#10768994)
Only if you postulate that your drives won't be able to saturate their respective number of PCIe lanes. The total number of lanes in the system is fixed by the choice of CPU, and having drives with a total lane count in excess of that only helps when your drives can't fully use the lanes they're given or if you're trying to maximize capacity rather than performance.