Microsoft Kernel Patch CPU Before and After Benchmarks Thread


Recommended Posts

  On 07/01/2018 at 17:26, Mockingbird said:

Which processor?

 

On Intel processors, Kernel VA shadowing is disabled if incompatible Anti-Virus is detected.

 

On AMD processors, Kernel VA shadowing is disabled.

Expand  

Ryzen 1700.

  On 07/01/2018 at 17:28, Mockingbird said:

As you can see, Kernel VA shadowing is off.

 

Everything is working as intended.

Expand  

Go read what I said again. You even quoted it.

  On 07/01/2018 at 17:31, Mockingbird said:

I don't even know what you are talking about.

Expand  

Clearly.

 

Otherwise you wouldn't have argued with me about the AMD user claiming performance loss when there was none, and would have also corrected yourself after seeing @Yogurth's link included post microcode update, which tends to clash with your posted post-microcode update screenshot,. Of which it seems to be a rather odd one-off, like the AMD user. Hence I posted what I did.

  On 07/01/2018 at 17:33, adrynalyne said:

Clearly.

 

Otherwise you wouldn't have argued with me about the AMD user claiming performance loss when there was none, and would have also corrected yourself after seeing @Yogurth's link included post microcode update, which tends to clash with your posted post-microcode update screenshot,. Of which it seems to be a rather odd one-off, like the AMD user. Hence I posted what I did.

Expand  

I don't thing there were many AMD users claiming performance because I have said, Kernel VA shadowing is disabled.

  On 07/01/2018 at 17:37, Mockingbird said:

I don't thing there were many AMD users claiming performance because I have said, Kernel VA shadowing is disabled.

Expand  

Just like there aren't many showing a 21% performance hit after microcode update. I'm glad we are now on the same page.

  On 07/01/2018 at 17:38, adrynalyne said:

Just like there aren't many showing a 21% performance hit after microcode update. I'm glad we are now on the same page.

Expand  

There hasn't been any microcode update from AMD (for these issues).

  On 07/01/2018 at 17:39, Mockingbird said:

There hasn't been any microcode update from AMD (for these issues).

Expand  

I didn't say there was. Go back and look at what I typed.

The AMD user was an example of a one-off, and most likely incorrect conclusion.

Your microcode update results are likely the same, which is why we need more microcode testing results.

Which @Yogurth supplied and confirmed my suspicions.

  On 07/01/2018 at 17:41, adrynalyne said:

I didn't say there was. Go back and look at what I typed.

The AMD user was an example of a one-off, and most likely incorrect conclusion.

Your microcode update results are likely the same, which is why we need more microcode testing results.

Which @Yogurth supplied and confirmed my suspicions.

Expand  

The "AMD user"?

 

Which "AMD user"?

  On 07/01/2018 at 17:42, Mockingbird said:

The "AMD user"?

 

What "AMD user"?

Expand  

Really? I linked the reddit url in this thread if you want to go look. Specifically, this is what I said:

  On 07/01/2018 at 16:33, adrynalyne said:

There hasn’t been enough testing with the microcode update to verify it. There is also a screenshot out there showing a massive performance hit after the meltdown patch on an AMD cpu. Just one that I saw. 

Expand  

One-offs never tell the whole story.

 

Edit: I posted it to a similar but different thread that spawned this one. Let me go find it.

Edited by adrynalyne
  On 07/01/2018 at 17:44, adrynalyne said:

Really? I linked the reddit url in this thread if you want to go look. Specifically, this is what I said:

One-offs never tell the whole story.

Expand  

Why would someone with an Intel Core i7-8700K be called the "AMD user"?   Facepalm.

 

I think you mean the "Intel user".

  On 07/01/2018 at 17:51, Mockingbird said:

Why would someone with an Intel Core i7-8700K be called the "AMD user"?   Facepalm.

 

I think you mean the "Intel user".

Expand  

No, you just don't understand what you are reading.

 

 

@Yogurthposted this.

Of which contains, this:

USPdAEX.png

 

  On 07/01/2018 at 17:53, adrynalyne said:

No, you just don't understand what you are reading.

 

 

@Yogurthposted this.

Of which contains, this:

USPdAEX.png

 

Expand  

 

"I found one on Russian forum. Can be fake"

 

There you have it.

  On 07/01/2018 at 17:59, Mockingbird said:

 

"I found one on Russian forum. Can be fake"

 

There you have it.

Expand  

OMG, stop being so obtuse.

 

"Can be fake" --yeah, so can yours.

Thats why...wait for it...wait for it...we need more microcode testing. Your argument for performance loss increase from microcode update after the OS patch is based upon a single microcode update-enabled test you posted.

 

  On 07/01/2018 at 18:01, adrynalyne said:

OMG, stop being so obtuse.

 

"Can be fake" --yeah, so can yours.

Thats why...wait for it...wait for it...we need more microcode testing. Your argument for performance loss increase from the OS patch is based upon a single microcode update-enabled test you posted.

 

Expand  

Someone with a Core i7-8700K and a ASUS PRIME Z370-A can easily run update his//her BIOS and run Realbench 2.56.

 

What you have posted has no context

  On 07/01/2018 at 18:04, Mockingbird said:

Someone with a Core i7-8700K and a ASUS PRIME Z370-A can easily run update his//her BIOS and run Realbench 2.56.

 

What you have posted has no context

Expand  

I'm done here because you are clearly trolling now.

 

I gave plenty of context for those who choose to see it. I'll try one last time and you can decide to be obtuse, or not. I don't care.

 

You posted a huge performance hit after microcode update. Just one. I believe it showed in the upwards of 21% performance loss?

Its not conclusive until the results can be verified and reproduced. That is just good investigation.

We've not seen enough evidence in bulk to verify how much a hit the microcode updates will actually have on performance.

@Yogurth posted results, upon which you said were without the microcode update. These conflicted with your 21% loss.

I explained, we need more microcode testing to verify the results of the performance hit (implying to what you posted). I gave an example of why more verification is needed because there was even an AMD user who claimed performance loss from the meltdown patch. No verification means its not really useful. Could it be fake? Yeah, it could. Could yours? Yeah they could. That iss why we need more testing.

@Yogurth later explained it was indeed was with microcode updates, also invalidating your claim, not by any fault of yours, but through the power of verification and further testing.

Then you invented this idiotic argument, of which I am done with.

 

I forgot to mention, there is an important bit of information in Techspot article for those who only checked results. Nvidia GPUs are most likely susceptible to meltdown attack and they are planning to issue a statement over this soon.

  On 07/01/2018 at 18:12, Yogurth said:

I forgot to mention, there is an important bit of information in Techspot article for those who only checked results. Nvidia GPUs are most likely susceptible to meltdown attack and they are planning to issue a statement over this soon.

Expand  

Interesting. Nvidia GPUs aren't x86 or ARM, are they? Honest question, I don't know.

 

  On 07/01/2018 at 18:13, adrynalyne said:

Interesting. Nvidia GPUs aren't x86 or ARM, are they? Honest question, I don't know.

Expand  

 

No idea either, but here is the quote from the article, if it helps... "On the GPU front, Nvidia is reportedly also affected, so there will be loads of additional tests to be done when "time comes. Our interpretation from Nvidia's blog is that they rely on CPU-like aggressive branch prediction on their GPU architectures. It's part of their performance gains over consecutive generations. The flaw appears to be the same as Intel CPUs, in that speculative operations occur without security checks first, as a secure design should be done."

So, I'm not sure if this has been covered (apologies if it has), but the Windows 10 Kernel patch is only half the story. We all need to apply BIOS updates to the various intel boards that we are using.

If you are worried about the performance hit on your intel PC, you need to re-test with the Windows 10 patch along side your motherboard manufacturers BIOS update that has the Intel CPU microcode update.

For those using Asus boards, they have annouced if your board has one of the following chipsets X299, Z370, Z270, Z170, B150, B250, H270, H170, H110, Q170, Q270 and finally X99 there should be an incoming BIOS update that contains the Microcode update (if its not already live).

Please see the following link for a full table of Motherboards, and the BIOS version containing the Microcode update: https://www.asus.com/News/V5urzYAT6myCC1o2

Hardware unboxed has done a benchmark video of a Z370 board with and without the latest Bios - all in all only a very small performance difference noticed in general. NVMe SSD performance does seem to be hit however:
https://www.youtube.com/watch?v=JbhKUjPRk5Q

Hope this helps.

  On 07/01/2018 at 18:12, Yogurth said:

I forgot to mention, there is an important bit of information in Techspot article for those who only checked results. Nvidia GPUs are most likely susceptible to meltdown attack and they are planning to issue a statement over this soon.

Expand  

Are you sure?:

  Quote

NVIDIA’s core business is GPU computing. We believe our GPU hardware is immune to the reported security issue and are updating our GPU drivers to help mitigate the CPU security issue. As for our SoCs with ARM CPUs, we have analyzed them to determine which are affected and are preparing appropriate mitigations. 

Expand  

https://forums.geforce.com/default/topic/1033210/nvidias-response-to-speculative-side-channels-cve-2017-5753-cve-2017-5715-and-cve-2017-5754/

  • Like 2
  On 07/01/2018 at 18:19, LimeMaster said:
Expand  

Like I said I do not know, I hope Techspot info is wrong, though Nvidia statement is already a few days older than the Techspot findings. Anything goes I guess.

  On 07/01/2018 at 18:24, Yogurth said:

Like I said I do not know, I hope Techspot info is wrong, though Nvidia statement is already a few days older than the Techspot findings. Anything goes I guess.

Expand  

I'm just worried we'll see more performance drops if it turns out their GPUs are affected.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Shotcut 25.07 by Razvan Serea Shotcut is a free, open source, cross-platform video editor for Windows, Mac and Linux. Major features include support for a wide range of formats; no import required meaning native timeline editing; Blackmagic Design support for input and preview monitoring; and resolution support to 4k. Editing Features Trimming on source clip player or timeline with ripple option Append, insert, overwrite, lift, and ripple delete editing on the timeline 3-point editing Hide, mute, and lock track controls Multitrack timeline with thumbnails and waveforms Unlimited undo and redo for playlist edits including a history view Create, play, edit, save, load, encode, and stream MLT XML projects (with auto-save) Save and load trimmed clip as MLT XML file Load and play complex MLT XML file as a clip Drag-n-drop files from file manager Scrubbing and transport control Video Effects Video compositing across video tracks HTML5 (sans audio and video) as video source and filters 3-way (shadows, mids, highlights) color wheels for color correction and grading Eye dropper tool to pick neutral color for white balancing Deinterlacing Auto-rotate Fade in/out audio and fade video from and to black with easy-to-use fader controls on timeline Video wipe transitions: bar, barn door, box, clock (radial), diagonal, iris, matrix, and custom gradient image Track compositing/blending modes: Over, Add, Saturate, Multiply, Screen, Overlay, Darken, Dodge, Burn, Hard Light, Soft Light, Difference, Exclusion, HSL Hue, HSL Saturation, HSL Color, HSL Luminosity. Video Filters: Alpha Channel: Adjust, Alpha Channel: View, Blur, Brightness, Chroma Key: Advanced, Chroma Key: Simple, Contrast, Color Grading, Crop, Diffusion, Glow, Invert Colors, Key Spill: Advanced, Key Spill: Simple, Mirror, Old Film: Dust, Old Film: Grain, Old Film: Projector, Old Film: Scratches, Old Film: Technocolor, Opacity, Rotate, Rutt-Etra-Izer, Saturation, Sepia Tone, Sharpen, Size and Position, Stabilize, Text, Vignette, Wave, White Balance Speed effect for audio/video clips Hardware Support Blackmagic Design SDI and HDMI for input and preview monitoring Leap Motion for jog/shuttle control Webcam capture Audio capture to system audio card Capture (record) SDI, HDMI, webcam (V4L2), JACK audio, PulseAudio, IP stream, X11 screen, and Windows DirectShow devices Multi-core parallel image processing (when not using GPU and frame-dropping is disabled) DeckLink SDI keyer output OpenGL GPU-based image processing with 16-bit floating point linear per color component ShotCut 25.07 changelog: Added a Whisper.cpp (GGML) model downloader to the Speech to Text dialog. A model is no longer included in the download and installation reducing their sizes. Improved the System theme to follow the operating system palette on Windows (darker and more contrast), and improved its appearance on macOS dark mode. Added Settings > Theme > System Fusion that combines the operating system palette with the monochrome, symbolic icons of the Fusion themes. Added an Outline video filter that uses the input alpha channel--useful with rich text or assets with a transparent background. This means that, like Drop Shadow, it will not work as expected when used after a text filter on a video or image clip. Rather, you must use a text clip (transparent color generator with text filter) on an upper track. Other New Features Added the ability to drag the waveform peak line to adjust audio gain. Added Settings > Timeline > Adjust Clip Gain/Volume to turn off the above. Added rolling an edit/trim to Timeline: Hold Ctrl (command on macOS) while trimming to simultaneously trim the neighbor clip. Added a Soft Focus filter set. Added Audio/Video duration to the Slideshow Generator dialog, defaults to 4 hours. This facilitates using Slideshow Generator to make transitions between everything when including both video and images. (It still respects the source duration and in & out points; duration here is a maximum.) Surround Sound Mixing Improvements Added fader and surround balance to the Balance audio filter if channels > 2. Added Channels toggle buttons to many audio filters: Band Pass Compressor Delay Downmix Equalizer: 3-Band Equalizer: 15-Band Equalizer: Parametric Expander Gain/Volume High Pass Low Pass Limiter Mute Noise Gate Notch Added support for 4 channels in the Copy Channel audio filter. For example, now you can: Copy stereo music to the rear channels and use the fader in the Balance filter to reduce its volume, Downmix spoken word into the center channel and apply a Band Pass filter to it, and Route music or sound effects to the low-frequency channels and apply a Low Pass filter to it. Other Improvements Changed the default Export > Audio > Rate control to Average Bitrate for AAC, Opus, and MP3. Added the ability to add/use multiple Mask: Apply filters. Added support for Scrub While Dragging to trimming on the timeline. Added hold Shift to ripple-trim when Ripple is turned off. Added French (Canadian) and Lithuanian translations. Fixes Fixed Mask: Apply with multiple Mask: Simple Shape (broke in v25.05) Fixed exporting projects containing only Generator clips on Windows (broke in v25.05). Fixed converting 10-bit full to limited range (broke in v25.01). Fixed dropdown menus using Settings > Theme > System on Windows. Fixed Balance and Pan audio muted channels if audio channels > 2. Fixed Export > Use hardware encoder fails with H.264 on macOS 15. Fixed Properties > Convert or Reverse for iPhone 16 Pro videos with Ambisonic audio. Fixed a single frame fade out filter would either mute or make black. Fixed repairing a project (e.g. broken file links) with proxy turned on. Fixed doing Freeze Frame on the first frame of a clip. Download: ShotCut 25.07 | Portable | ARM64 ~200.0 MB (Open Source) View: Shotcut Home Page | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Win8 still takes the crown though in terms of worst Microsoft OS which all boiled down to it's horrible interface upon release as it was actually difficult to do even basic stuff. I remember trying it in a VM early on and it was a chore doing the basics we have had for ages and I quickly dumped that and never bothered with it again. in fact, prior to Win11 it was the only OS from Microsoft I have never used/had on a real machine and I have been using windows from Win v3.11 in mid-1990's through Windows 10. basically Win v3.11, 95, 98, Me, 2k, XP, 7, Vista, 10. but putting Windows 8 aside, I would probably place Win11 next in line (lets start from WinXP to date since that's basically when Windows got good and PC's pretty much went mainstream), but at least Win11 is not in the 'horrible' category as at least it's basic interface is normal. but if I ignore the interface, Win11 is a strong candidate, not only for telemetry and the like, but forced "requirements" which make people jump through hoops we should not have to all in the name of "better security", which personally I think is not enough of a boost to justify the forced "requirements". but one area you can tell Linux is faster is installing updates and, as a bonus, we generally don't need to reboot (short of like Kernel updates but those I am in no rush as my longest every main PC system uptime without a reboot was Aug 2023 until Jan 2025). but yeah, I suspect all of the background junk Windows has running does slow things a bit. p.s. speaking of that 'CachyOS', I used one of their custom Proton's (on Lutris) to get NTSync recently as while I usually use the more typical 'GE-Proton10-10' (this and '10-9' have NTSync support which was added recently. but 10-9 you have to manually enable where as 10-10 is automatic if it's available in the kernel to the system), I have one game which does not play back in-game videos with the Proton 10 series (you can hear audio but it's basically a black screen) but works in the 9 series and 'CachyOS' had a build from Jan 2025 that has NTSync, so I used that and it worked. I had to use 'PROTON_USE_NTSYNC=1' though since it's not enabled by default (along with 'sudo modprobe ntsync', or setup a udev rule etc if you want it to work in reboots without needing to do that command). one can see NTSync is working through MangoHud if you setup 'winesync' (just add that entry to "~/.config/MangoHud/MangoHud.conf") in the configuration file for ManngoHud or if you want to directly see it in proton log I did 'PROTON_LOG=1', which then creates a log in the Home folder which, at least on GE-Proton10-10, creates 'steam-default.log' and in that shows "wineserver: NTSync up and running!" where as if you don't it will generally show "fsync: up and running."
    • Riverdale... in space? Hope not.
    • Then why didn't Apple upstream their feature?
    • Unix is in fact not open source.
  • Recent Achievements

    • Week One Done
      Lokmat Rajasthan earned a badge
      Week One Done
    • One Month Later
      TheRingmaster earned a badge
      One Month Later
    • First Post
      smileyhead earned a badge
      First Post
    • One Month Later
      K V earned a badge
      One Month Later
    • Week One Done
      K V earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      638
    2. 2
      ATLien_0
      241
    3. 3
      Xenon
      177
    4. 4
      neufuse
      155
    5. 5
      +FloatingFatMan
      123
  • Tell a friend

    Love Neowin? Tell a friend!