Any idea what impact the patches to Linux and Windows to address the Intel cpu flaw will likely have on typical DataStage workloads?
I've been reading that workloads with lots of network and i/o may be worst hit with up to a 30% performance drop.
Intel Kernel design flaw / bug
Moderators: chulett, rschirm, roy
Ah... hadn't heard of this yet but was just reading about their "Page Table Isolation" issue in articles like this one and this one. Thankfully, gaming performance doesn't seem to be effected but who games on a Linux box anyway?
There seems to be a lot of "depends" around this, for example from the second link:
There seems to be a lot of "depends" around this, for example from the second link:
Performance penalties from single to double digits are expected on patched kernels. The penalty depends upon how much interaction the application/workload deals with the kernel if there's a lot of context switching and other activity. If it's a simple user-space application not doing much, the x86 PTI additions shouldn't cause much of an impact. Newer Intel CPUs with PCID should also help in ensuring less of a performance impact.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
I just read about this topic. Nasty
pushing out patches to a raised floor area is never easy or fast. Big companies will most likely lag on this patching for their ETL environments.
But ya... it would be interesting to see the hit on DataStage.
If someone out in the wild is about to patch this... please share your results with us. Select a good meaty job to run. Not a 2 min job.
Do a pre/post patch run of course.
Application restart times logged, etc...
pushing out patches to a raised floor area is never easy or fast. Big companies will most likely lag on this patching for their ETL environments.
But ya... it would be interesting to see the hit on DataStage.
If someone out in the wild is about to patch this... please share your results with us. Select a good meaty job to run. Not a 2 min job.
Do a pre/post patch run of course.
Application restart times logged, etc...
Now it sounds like there are two vulnerabilities and one of them is not limited to Intel CPUs as it affects a lot of CPU types including IBM POWER...
https://www.ibm.com/blogs/psirt/potenti ... er-family/
https://www.ibm.com/blogs/psirt/potenti ... er-family/
Choose a job you love, and you will never have to work a day in your life. - Confucius
we knew it was going to be brutal though. You can't really patch a CPU. The BIOS, but not the actual CPU chip. So they *have* to be jacking in a software solution that bypasses the hardware flaw which *has* to be a ton slower. This is on par with taking the math coprocessor off the chip for us old guys
I prefer "seasoned" or "experienced"... thank you!UCDI wrote:...This is on par with taking the math coprocessor off the chip for us old guys
...and yes - this is going to be a real pain if your system is already stressed.
One of the major game platforms patched their Linux servers and said they saw a "hit in excess of 20% of performance capacity".