For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Lightboard Lessons: CPU Hyper-Threads and TMM

In this episode of Lightboard Lessons, Jason details how BIG-IP’s Traffic Management Microkernel (TMM) utilizes Intel’s Hyper-Threading Technology (on applicable platforms) and the impacts depending ...
Published Sep 06, 2017
Version 1.0
application delivery
lbl
TMOS
JRahm's avatar
Icon for Admin rankAdmin
Christ Follower, Husband, Father, Technologist. I love community and I especially love THIS community. My background is networking, but I've dabbled in all the F5 iStuff, I'm a recovering Perl guy, and am very much a python enthusiast. Learning alongside all of you in this accelerating industry toward modern apps and architectures.
View Profile
JRahm's avatar
Icon for Admin rankAdmin
Christ Follower, Husband, Father, Technologist. I love community and I especially love THIS community. My background is networking, but I've dabbled in all the F5 iStuff, I'm a recovering Perl guy, and am very much a python enthusiast. Learning alongside all of you in this accelerating industry toward modern apps and architectures.
View Profile
dragonflymr's avatar
dragonflymr
Icon for Cirrostratus rankCirrostratus
Sep 26, 2017

Hi,

 

I am back :-)

 

Some more questions:

 

HTSplit and vCMP - is same rule about even and odd virtual cores apply to vCMP guest? What when we have 1 vCPU vGuest?

 

ASM - according to KB ASM is using highest numbered core for part of control plane tasks. Same rule about halting 80% of odd core still applies here - so ASM control plane processes will be throttled to 20% if even core is loaded over 80%?

 

Is ASM really limited for those selected control plane task to one and only one core? I've seen configs where highest numbered core was almost constantly loaded 90-100% - I assume mainly by ASM control plane, if only one core can be dedicated to ASM what is an option in such case?

 

Piotr