openStack 云平台管理节点管理网口流量非常大 出现丢包严重 终端总是时常中断问题调试及当前测试较有效方案

tuning for Data Transfer hosts connected at speeds of 1Gbps or higher

<一.本次OpenStack系统调试简单过程简单记录>

1,dmesg 日志,丢包问题关键原因定位;

[101231.909932] net_ratelimit: 85 callbacks suppressed

2,ethstatus -i p5p1 实时追踪网口TX/RX状态;

3,具体内核等相关参数调整

# recommended default congestion control is htcp 超文本缓冲net.ipv4.tcp_congestion_control=htcp# recommended for hosts with jumbo frames enabled   开启系统巨型帧net.ipv4.tcp_mtu_probing=1

you should leave net.tcp_mem alone, as the defaults are fine. A number of performance experts say to also increase net.core.optmem_max to match net.core.rmem_max and net.core.wmem_max, but we have not found that makes any difference. Some experts also say to set net.ipv4.tcp_timestamps and net.ipv4.tcp_sack to 0, as doing that reduces CPU load. We strongly disagree with that recommendation for WAN performance, as we have observed that the default value of 1 helps in more cases than it hurts, and can help a lot

sysctl net.ipv4.tcp_available_congestion_control
/sbin/modprobe tcp_htcp/sbin/modprobe tcp_cubic
sysctl -w net.ipv4.tcp_congestion_control=htcp
 /sbin/ifconfig ethN txqueuelen 10000

经过相关参数调整,ssh远程终端不再出现时常连接中断大延迟卡顿,云平台管理portal 大延迟Loading加载等问题,后续问题继续观察测试中!

<二.附加linux tunning,网络部分及内核参数,UDP/TCP tunning>

https://www.myricom.com/software/myri10ge/347-what-is-the-performance-impact-of-vlan-tagging-with-the-myri10ge-driver.html

1,What is the performance impact of VLAN tagging, slight performance impact incurred when using VLAN tagging;

There are two issues:

  1. Capabilities of vlan shim drivers to do offloads

    On all OSes, there is a shim driver to handle vlan traffic and configuration. This driver sits between the TCP/IP stack and the hardware driver. On Windows, every hardware vendor must ship their own vlan shim driver. (Our Windows VLAN driver is included in the Windows Myri10GE software distribution on the Myri10GE Download page). However, on linux, the vlan shim driver is shared by all adapters, regardless of vendor. It is not, to our knowledge, possible to bypass this shim driver.

    Prior to linux 2.6.26, the linux vlan driver did not propagate any advanced offload flags from the hardware device to the vlan shim device. That means, for example, that doing TCP Segmentation Offload was not possible on a vlan device, even though the driver/hardware supports it. This is true for all vendors, not just our hardware.

    There are other limitations. For example, prior to 2.6.32, the vlan driver would xmit all packets through tx queue 0, rather than the correct TX queue. RHEL 5.5 enables TSO on VLAN, but does not enable S/G, which results in a memory copy of most packets, etc.

  2. Capabilities of the adapter to handle vlan packets

    Our adapter handles VLAN traffic where it is required to (emitting TSO frames, for example).

What is the performance impact of VLAN tagging

时间: 2024-03-02 23:43:11

openStack 云平台管理节点管理网口流量非常大 出现丢包严重 终端总是时常中断问题调试及当前测试较有效方案的相关文章

大数据云计算openstack云平台基础到精通实践视频教程

38套大数据,云计算,架构,数据分析师,Hadoop,Spark,Storm,Kafka,人工智能,机器学习,深度学习,项目实战视频教程 视频课程包含: 38套大数据和人工智能精品高级课包含:大数据,云计算,架构,数据挖掘实战,实时推荐系统实战,电视收视率项目实战,实时流统计项目实战,离线电商分析项目实战,Spark大型项目实战用户分析,智能客户系统项目实战,Linux基础,Hadoop,Spark,Storm,Docker,Mapreduce,Kafka,Flume,OpenStack,Hiv

zabbix使用fping监控任意两个节点之间的网络质量、丢包率和响应时间

zabbix使用fping监控任意两个节点之间的网络质量.丢包率和响应时间 之前的博文 使用zabbix3.0.4的ICMP Ping模版实现对客户端网络状态的监控 https://www.cnblogs.com/reblue520/p/6832059.html 只能监控zabbix server到zabbix_agent之间的网络情况,不能监控任意两点间的网络情况 此次的方法可以监控任意两点之间的网络情况 需求: mysql主从之间同步经常会延迟,为了查看是否网络问题,先添加两个节点之间的网络

Netweaver和SAP云平台的quota管理

Netweaver 以需要为一个用户上下文(User Context)能够在SAP extended memory区域中分配内存尺寸创建quota为例. 对于Dialog工作进程,使用事务码修改参数 ztta/roll_extension_dia. 对于非Dialog工作进程,quota参数为ztta/roll_extension_nondia.可以用关键字quota搜索更多RZ11参数. CloudFoundry Quota不够会怎样?当我试图部署一个应用到SAP云平台的neo环境时,可能会遇

云平台中节点异常如何考虑迁移因素

在云平台中物理节点异常是否立即迁移到其他可用资源节点?还是人为干预? 手动恢复异常节点的云主机...? 自动迁移实现不难,难就难在如何定位故障?物理机异常有N种假设: 网络故障:交换机端口异常,广播风暴... 这种现象将会导致多节点异常?如果这种故障实现自动迁移将会带来意外风险 服务异常:MQ 消息积压,磁盘写满,将会导致所有节点无法正常通信,如果这种故障实现自动迁移带来意外风险 软件异常:后端存储节点服务down ,monitor 异常,将会导致云主机无法正常work, 如何定位VM 故障,是

OpenStack云平台的网络模式及其工作机制

网络,是OpenStack的部署中最容易出问题的,也是其结构中难以理清的部分.经常收到关于OneStack部署网络方面问题和OpenStack网络结构问题的邮件.下面根据自己的理解,谈一谈OpenStack的虚拟网络.网络拓扑和网络流.个人理解有限,仅抛砖引玉,有问题请指正,谢谢. 一.相关概念和要点(可跳过) 1.OpenStack中nova-network的作用 OpenStack平台中有两种类型的物理节点,控制节点和计算节点.控制节点包括网络控制.调度管理.api服务.存储卷管理.数据库管

OpenStack云平台开启常用端口

2017年2月6日 17:21 项目==>计算==>访问和安全==>用户所在组一栏的 管理规则 进入"管理安全组规则"界面,可查看已存在的端口 +添加规则 设置选项: 定制TCP规则 方向: 入口与出口各添加端口一次, 打开端口 | 起始端口号: 开启单一端口或指定起始端口号 终止端口号: 输入结束范围 远程 CIDR CIDR: 0.0.0.0/0 设置好后点击"添加" 返回"管理安全组规则"查看添加好的端口

制作OpenStack云平台centos6.5镜像

创建虚拟镜像 # qemu-img create -f raw Cloud_Centos6.5_64bit.img 10G [[email protected] ~]# ll /opt/CentOS-6.5-x86_64-bin_DVD.iso -rw-r--r-- 1 root root 4471971840 Aug 21 2016 /opt/CentOS-6.5-x86_64-bin_DVD.iso [[email protected] ~]# [[email protected] ~]#

openStack 云平台使用一般杂记

1. To launch an instance,you must at least specify the flavor,image name,network,security group,keypair,and instance name; 2. A flavor specifies a virtual resource allocation profile which includes processor,memory,and storage; nova get-vnc-console i

【VMCloud云平台】SCO(七)如何使用集成包

上一篇我们介绍了什么是集成包,本篇我们将介绍如果将导入的集成包进行部署并设置,最终交付使用(下图红色为部署中,紫色为实施完成,蓝色为计划中): 1. 我们打开SCO01上的Deployment Server,找到左侧集成包,右键选择第二项: 2. 接着我们在欢迎界面上点击下一步: 3. 选择上一篇我们导入的OIP包: 4. 选择SCO01并进行添加: 5. 点击下一步后,这里可以计划安装也可以立即导入,由于我们并没有正式流程在跑,这里就选择立即导入即可: 6. 在摘要页上点击完成即完成IP包部署