TL DR, we stress tested our applications before and after the patch, and the difference was negligible enough to consider it performing pretty much the same. Performance before and after from a litany of burn-in tests came back pretty much within the expected variance. One interesting t hing on SQL, is before we had a few spikes in utilization, after, for the exact same test, it was more stable, no spikes at all.įor RabbitMQ, which is opensource, we saw another 2% increase in memory and CPU.Ĭonsidering we run pretty 'loose' with our VM's and none of them are over 60% capacity during normal use, we had enough headroom to work with the 30-40% increase, but do not need it. SQL we actually saw a reduction in memory, but probably due to the reboot needed, however CPU and I/O stayed constant. Net back in microservices no change at all IIS on 2012r2, 2% increase in memory utilization, <1% on CPU We saw no real performance impact on any of our tests when compared to our APM baselines before enabling the keys. Ivy Bridge, and Haswell ESXi hosts, Skylake Physical SQL clusters. We deployed in our Test Lab, which has full versions of a few of our applications. I'm about to have a meeting here in a bit where I let the devs unleash their testing in the lower non-production environments. Everything we tested, pushing the limits beyond what we see in day to day operations showed a less than 3% max variance from before enabling the patch to after. Most virtual with ESXi 6.0 backend, patched (but not the microcode update patch) and a few physical clusters for SQL. We used that for the Meltdown patch (no BIOS updates for Spectre variant 2) and mostly Haswell, Skylake and Ivy Bridge hardware. We have a walled off performance lab with several of our applications set up for performance testing, pushing it the max to get more accurate KPI's. I didn't spend millions on APM and hardware performance tools to use your stuff, but then again maybe the advert is for a small mom-pop shop. "Install in a lab and test using our software". THat looks like more of an advertisement than a guide. At this time these include, but are not limited to, HPE and VMWare. Several vendors have pulled existing updates with the Spectre Fix. UPDATE : If you have already deployed BIOS/Firmware updates, or if you are about to, check your vendor. Please continue to stay vigilant with your patching and updating research, and remember to use test environments and small testing groups before doing anything hasty. UPDATE : There are still patches being released (and pulled) by vendors. Please continue to research and test any and all patches in a test environment before full implementation. UPDATE : Intel has announced new Microcode for several products, which will be bundled in by OEMs/Vendors to fix Spectre-2 (hopefully with less crashing this time). If anyone is a better UI/UX person than I, feel free to edit it to make it look nicer. More information will be added (MacOS, Linux flavors, Windows 7-10, etc.) and it will be cleaned up as we go. It's a little rough around the edges, but it outlines steps needed for Windows Server admins to update their systems in regards to Meltdown & Spectre. UPDATE : I have added a page to the /r/sysadmin wiki: Meltdown & Spectre. Otherwise, we will be locking and/or removing new threads that could easily be discussed here. If an existing thread has gained traction and a suitable amount of discussion, we will leave it as to not interrupt existing conversations on the subject. I will try to keep this updated when major information comes available. Please direct your questions, answers, and other comments here instead of making yet another thread on the subject. Due to the magnitude of this patch, we're putting together a megathread on the subject.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |