Date: Wed, 20 Feb 2019 19:02:01 -0330 From: "Jonathan Anderson" <jonathan@FreeBSD.org> To: "Alex Dupre" <ale@FreeBSD.org> Cc: "Colin Percival" <cperciva@freebsd.org>, "Matthew Seaman" <matthew@FreeBSD.org>, freebsd-hackers@freebsd.org Subject: Re: Amazon AMIs Message-ID: <E396A0C7-F939-48A1-9B57-D643806B303B@FreeBSD.org> In-Reply-To: <53a0bd68-a6ba-e8ad-4af2-abeb22e92c03@FreeBSD.org> References: <f002c020-1e63-c12f-456e-e20f8546a701@FreeBSD.org> <8a139c9c-b98b-4a54-1d7c-0ea1e3dc7a72@freebsd.org> <53a0bd68-a6ba-e8ad-4af2-abeb22e92c03@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 20 Feb 2019, at 18:50, Alex Dupre wrote: > Colin Percival wrote: >> Last time I looked at this, we weren't handling hotplug/hotunplug of >> "NVMe" >> disks properly on the m5/c5/etc. instances. I opted to recommend the >> instance >> which completely works rather than the one with slightly better >> performance... > > It does happen only on a few instances, but I get some freezes on new > t3 > machines: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235856 > > They are indeed cheaper and more performant, but not 100% reliable in > every workload. https://www.xkcd.com/937 ? :) Jon -- Jonathan Anderson jonathan@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E396A0C7-F939-48A1-9B57-D643806B303B>