My neighbours were really funny.

The moment I pointed out to them using thestar newspaper, they seem to be 'shocked'.

They asked a lot about maxis RM89 30Mbps and TM RM79 30Mbps. I had to explain to them on TM 60gb quota.

Then I said, "K lah, if you guys don't wanna share anymore, good luck on getting new port for your own fiber. Our district doesn't have vacant fibre port anymore"

Cue further explaination.....

Considering House A neighbours only pay RM50 each for current unifi 500Mbps for me......(what....sharing with total 4 houses including mine)......3 of my neighbours household 'representative' agreed to continue sharing....

This evening = will hold meeting with House B neighbours.....

So far, the microcode patch issue only happen with windows 7 and 10. See for yourself on the impact of speed after latest microcode was applied.

I made some post on ivy bridge 3570k performance when the first spectre microcode was released.
https://forum.lowyat.net/topic/4547450

Then another posts on someone thread where the guy has haswell CPU.
https://forum.lowyat.net/index.php?showtopic=4649008
Had to inform the guy that latest microcode from intel somehow has less performance impact as I also have problem with the older haswell microcode for my i3-4330 and I5-4200U.

Linux and MacOS seem to have lesser performance penalty due to usage of retpoline.
However, after reading this https://bbs.archlinux.org/viewtopic.php?id=241738 , it seem as if the performance penalty also exists, although still less severe compared to windows   .....someone might wanna reply at this archlinux forum......blacktubi, you wanna reply at that thread that the poster issue was caused by older microcode?   Latest haswell ULT microcode is 24, version 23 is haswell ULT problematic patch.

For one, Microsoft doesn't push microcode update for Win7, thus you shouldn't worry about it........unless if your hand is itchy and you wanna mod the bios, then you better make sure you select the correct microcode version.

Some mainboard vendors are very consumers friendly[I]......where vendors actually release bios with Spectre protection.......but they don't release bios with Spectre-NG protection (which somehow reduced the performance penalty). 
So, if you are one of 'lucky' user, the only choice is to either fully disable spectre mitigation via registry or use the Intel Microcode Boot Loader.
I modded the bios and so I know the problem also occurred for win7.

But just to be sure, you better check the microcode version via RWEverything --->Access--->CPU MSR
Then compare both CPU ID and PATCH ID (this is the microcode version) with information from Intel pdf sa00115-microcode-update-guidance. If the patch ID is same as 'Pre-Mitigation Production MCU', err......my condolences. 

It is very strange that biloxee doesn't encounter this issue for his win10.