Most manufacturers would simply attempt to use SMP to distribute TMOS process across multiple processors—with shared memory, network card, and special purpose processors. Others might attempt to run multiple instances of the TMM on different processors—still with the requisite shared memory, network card, and special-purpose processors. Instead, CMP(clustered multiprocessing) enables load balancing of multiple processing cores, each with its own dedicated memory, network interface, and special-purpose processors. Each core runs its own, completely independent TMM process. By separating the dependencies between the instances, CMP allows more of the traffic management process virtually the entire process to be parallelized. This provides a substantial benefit to the overall performance of the system.The hardware that enables CMP is comprised of two important, proprietary F5 technologies: the Disaggregator and the High Speed Bridge (HSB).
The Disaggregator acts as a hardware-based load balancer, distributing traffic flows between the independent TMM instances and managing flow affinity if or when necessary. Not only does this facilitate a near 1:1 linear performance growth (doubling the number of processing cores nearly doubles the computing power with no diminished returns), but it completely virtualizes the processing cores from the system and the other cores. This provides high availability and reliability in the event that any core becomes non-functional.
The HSB delivers direct, non-blocking communication between the TMM instances and the outside world without the loss normally associated with Ethernet interconnects. It also provides the streamlined message-passing interface that enables TMM instances to share information. This provides the unsurpassed throughput and interconnectivity of each processor’s dedicated network interfaces. It also mitigates the performance impact of inter-process communications in the few remaining instances where it takes place.

The rules has been changed by CMP
The amount of performance increase that can be expected by parallelizing a process is a factor of the amount of the process that can truly be parallelized. If a process requiring 10 units of time can only be 50 percent parallelized, the process will never run in less than five units, even if the parallelized portion is processed instantly. As a result, the entire process can never be more than twice as fast.
Up until now, the game has been pretty simple—and widely understood. First, it was to optimize your code to run on a single processor as best you can and ride the “Intel power-curve.” Then, it was to optimize your code for SMP or AMP and then build your platforms with as many processing cores as possible. All the while, performance improvements have slowly dwindled to miniscule amounts.
CMP changes the rules of the game. Instead of working to continually improve the performance of a never-changing proportion of parallelized processes, CMP’s most basic tenant is to change that proportion. Continuing improvements in performance can only be realized by increasing the amount of the application delivery process that can be parallelized. Only parallelizing nearly all of that process can enable near 1:1 linear scaling—fully utilizing all the processing cores.

转载于:https://blog.51cto.com/ipneter/370040

F5 CMP architecture相关推荐

  1. project web architecture

    http://www.alexa.com/topsites 2012中国软件开发者大会(SDCC) http://www.csdn.net/article/a/2012-09-08/2809730 于 ...

  2. 【论文阅读】ICLR 2022: Scene Transformer: A unified architecture for predicting future trajectories of ...

    ICLR 2022: Scene Transformer: A unified architecture for predicting future trajectories of multiple ...

  3. 激光雷达Lidar Architecture and Lidar Design(下)

    激光雷达Lidar Architecture and Lidar Design(下) Considerations on Lidar Design 双基地还是单基地? 双轴还是同轴? 几何重叠 向上还 ...

  4. 激光雷达Lidar Architecture and Lidar Design(上)

    激光雷达Lidar Architecture and Lidar Design(上) 介绍 激光雷达结构: 基本条件 构型和基本布置 激光雷达设计: 基本思想和基本原则 总结 介绍 激光雷达结构是激光 ...

  5. NVIDIA Turing Architecture架构设计(下)

    NVIDIA Turing Architecture架构设计(下) GDDR6 内存子系统 随着显示分辨率不断提高,着色器功能和渲染技术变得更加复杂,内存带宽和大小在 GPU 性能中扮演着更大的角色. ...

  6. NVIDIA Turing Architecture架构设计(上)

    NVIDIA Turing Architecture架构设计(上) 在游戏市场持续增长和对更好的 3D 图形的永不满足的需求的推动下, NVIDIA ®已经将 GPU 发展成为许多计算密集型应用的世界 ...

  7. ffmpeg architecture(下)

    ffmpeg architecture(下) 第3章-转码 TLDR:给我看代码和执行. $ make run_transcoding 我们将跳过一些细节,但是请放心:源代码可在github上找到. ...

  8. ffmpeg architecture(中)

    ffmpeg architecture(中) 艰苦学习FFmpeg libav 您是否不奇怪有时会发出声音和视觉? 由于FFmpeg作为命令行工具非常有用,可以对媒体文件执行基本任务,因此如何在程序中 ...

  9. ffmpeg architecture(上)

    ffmpeg architecture(上) · 视频-您看到的是什么! · 如果您有一系列图像序列,并以给定的频率(例如每秒24张图像)进行更改,则会产生运动的错觉.总之,这是视频背后的基本概念:一 ...

最新文章

  1. 老李推荐:第5章5节《MonkeyRunner源码剖析》Monkey原理分析-启动运行: 获取系统服务引用 1...
  2. 【中继协助频谱切换】基于中继协助的频谱切换机制的MATLAB仿真
  3. Visual Studio 2013开发 mini-filter driver step by step 内核中使用线程(7)
  4. android11开启无线调试
  5. 数据分析与挖掘-python常用数据预处理函数
  6. sublime用cmd窗口调试python_如何使用xdebug和sublime调试python脚本
  7. seata分布式事务原理_又见分布式事务之Seata
  8. 软工作业4:词频统计
  9. jQuery常用工具方法
  10. python必备基础代码-python基础知识和练习代码
  11. 一起学JAVA 接口 面向接口开发
  12. 502 Bad Gateway错误
  13. uni-app 小程序后端返回二进制流图片显示
  14. 理想主义者与现实主义者的差别
  15. Windows7使用inter7代cpu更新补丁问题
  16. es高级客户端聚合查询api快速入门
  17. 苹果怎么设置下载软件不要密码?手机技巧分享
  18. Dubbo 的集群容错模式:Failover Cluster
  19. 在Windows上抓取Android手机的网络流量(另类用法-使用CainAbel + WireShark)
  20. 八道二叉树基础程序面试题

热门文章

  1. HP officejet、PageWide打印机任意代码执行漏洞cve-2017-2741 Tenable发布漏洞检测插件...
  2. Codeforces 38B - Chess
  3. MySQL 5.7 for Windows 解压缩版配置安装
  4. Python学习第三天--数据类型
  5. AFNetworking 下载文件断点续传操作
  6. 详解Android实现全屏正确方法
  7. 富友电子商务系统的四大优势助网商轻松赚钱
  8. Android的短信接收类
  9. 我的世java途径错误_我的世界JAVA路径错误的解决方法分享
  10. 【MySQL】MySQL开发注意事项与SQL性能优化步骤