2990WX is 1800$
>In games
>In single threaded Adobe Photoplop
>In shitty PS2 emulators
OK
Ironic retardation is still retardation.
Photoshop been multi-core/threaded since CS 6.
PCSX 2 been using at least 2+ cores/threads since 0.9.5 (it's 1.4.0, currently).
>i lose money
>lose a fuck ton of money for staying on intel for years on end instead of switching to epyc
Did you not read the part where I said a minute of downtime = millions of dollars? That's no small drop in the bucket. Also, power consumption costs for the newer Skylake Xeons and the EPYC servers were about equal. Neither of them produced any more heat than the Haswell machines, nor did we had any hardware compatibility issues that needed to be addressed. I think EPYC needed some of our VMs to be recreated because of a fault that AMD have addressed by now.
>stay on xeon platform with inferior performance and power consumption and a fuck ton of security holes
It's not like we had a choice. Intel knows this and upped the pricing for near-equivalent Skylake Xeons. We paid about $5-12k more per server, but that's still more favorable than losing hundreds of millions because our company's day-to-day operation ground to a fucking halt. And yes, we operate in several different time zones, so there was no time period that would have reduced our losses even more.
>Sounds like Intel has you by the balls
It's VMWare too. I'm pretty sure they could make live migration possible between two x86-64 architectures if we can migrate Core2-era Xeons to Haswells without a problem.
>You could of course make a copy of the cluster oonto the new servers and when ready flip the switch to AMD
That's pretty much what we planned, but there are still thousands of users/services that still need to access VMs on those servers and any changes that are made between us copying those instances and bringing the new hardware online would be lost. That's why live migration is so important and planning for service outages is not as simple as shutting down one server and flipping the switch on another.
Now this is EPYC!
>It's not like we had a choice.
Well then you're free to stay on a shitty inferior platform while all the other companies switch to Epyc because "i'm gonna lose 6 gorillion dollars"
>a minute of downtime = millions of dollars
Lesser problem/damage than being fucked completely via Meltdown/Spectre or other secuiry hole.
Also, you're a fucking retard if you think that up to -57% of performance loss in enterprise/server and MySQL due to "full MeltDown patch" is thing that should be ignored "just because I'm afraid of a little downtime which can cost a couple mils". -57% in performance loss equals massive slowdowns AND downtime for end user, which in itself translates to massive loss of credibility as a service, loss of clients, which in itself leads to monetary losses even bigger than that of a "slight downtime due to change from Xeon to Epyc". You are a fucking moron that doesn't know how to do business and I hope your company goes fucking bankrupt, because there are such idiots like you working in it.
He's probably larping but can't be absolutely sure.
Just wait until the partners switch to a provider that uses AMD.