Cloud Native应用交付
  • 首页
  • 关于本站
  • 个人介绍
  • Downloads
  • Repo
    • Github
    • Container
  • F5
    • F5 Python SDK
    • F5-container
    • F5-LBaaS
  • 社交
    • 联系我
    • 微信/微博
    • 公众号
    • 打赏赞助
行至水穷处 坐看云起时
☁️We are in new App Mesh era: imesh.club ☁️
  1. 首页
  2. F5技术
  3. 正文

rule优化技巧【更新中】

2008年12月12日 3651点热度 0人点赞 0条评论

It's better to use a directly-indexed array (i.e. $::my_array(my_index) ) than to use switch or matchclass (again, assuming your data doesn't need to be dynamic); (this is likely because matchclass requires calling a function, and includes additional matching features that cost CPU cycles)

 

It's better to use a command like [HTTP::uri] than to place the value in a variable (tested up to 20 re-uses, it did not seem to be converging -- variables appear to always be more expensive). (this is likely due optimization which caches the result of commands in case they are re-used)

 

 

The amount of code in an unused switch statement or an un-called if block doesn't seem to be a performance consideration. Only worry about what code is executed.

 

It's better to use "switch" than any form of "if", whenever possible (likely due to the added expression evaluation in "if")

 

It's better to use chained "if"/"elseif" statements than to use separate "if" statements (likely due to "if"/"elseif" being a single statement so fewer commands are lookup up and run, and fewer return values must be considered).

It's better to use "switch" (even with -glob) instead of "matchclass" for comparisons of 100 elements or less (and of course only if your data does not need to be dynamic); (this is likely due to matchclass using md5 as it's hash)

 

 

本作品采用 知识共享署名 4.0 国际许可协议 进行许可
标签: oneconnect TCP fin ack http profile
最后更新:2008年12月12日

纳米

http://linjing.io

打赏 点赞
< 上一篇
下一篇 >

文章评论

取消回复

纳米

http://linjing.io

☁️迈向Cloud Native ADC ☁️

认证获得:
Kubernetes: CKA #664
Microsoft: MCSE MCDBA
Cisco: CCNP
Juniper: JNCIS
F5:
F5 Certified Solution Expert, Security
F5 Certified Technology Specialist, LTM/GTM/APM/ASM
F5 Certified BIG-IP Administrator
  • 点击查看本博技术要素列表
  • 分类目录
    • Avi Networks (3)
    • Cisco ACI (1)
    • CISCO资源 (21)
    • F5 with ELK (8)
    • F5-Tech tips (38)
    • F5技术 (203)
    • Juniper (4)
    • Linux (7)
    • Nginx (18)
    • SDN (4)
    • ServiceMesh (19)
    • WEB编程 (8)
    • WINDOWS相关 (7)
    • 业界文章 (18)
    • 交换机技术 (20)
    • 化云为雨/Openstack (35)
    • 协议原理 (52)
    • 容器/k8s (64)
    • 我的工作 (19)
    • 我的生活 (70)
    • 网站技术 (19)
    • 路由器技术 (80)
    • 项目案例 (28)
    文章归档
    标签聚合
    F5 k8s openstack nginx istio DNS envoy gtm docker network flannel api irule bigip neutron cc kubernetes ELK vxlan BGP dhcp VPN IPSec lbaas ingress ingress controller nginx plus sidecar IPSec VPN NAT sql
    最新 热点 随机
    最新 热点 随机
    Say hello for 2021 二进制flannel部署,非cni网络模式下与k8s CIS结合方案 又是一年国庆 Service Account Token Volume Projection Istio ingressgateway 静态TLS证书加载与SDS发现方式配置区别 Istio里Gateway的port定义与实际ingressgateway的listener端口关系及规则 Helm 3 部署NGINX Ingress Controller 应用交付老兵眼中的Envoy, 云原生时代下的思考 Istio sidecar iptables以及流量控制分析 Istio 熔断策略及envoy配置
    Say hello for 2021
    [转]CISCO IOS ?下出现的命令帮助 最近工作 ICMP TYPE CODE 对应表 k8s里各种证书配置关系解释 F5-ltm官方对 IIS上http的profile设置建议 常见路由器关闭端口 kubernetes一些概念 配置同步时产生的UCS下包含的文件和目录以及排除的文件及目录 Kubernetes 1.6.7三节点集群初始信息输出 升级BLOG
    链接表
    • Jimmy Song‘s Blog
    • SDNap
    • SDNlab
    • SDN论坛
    • Service Mesh社区
    • 三斗室
    • 个人profile

    COPYRIGHT © 2020 Cloud Native应用交付. ALL RIGHTS RESERVED.

    THEME KRATOS MADE BY VTROIS

    京ICP备14048088号-1

    京公网安备 11010502041506号

    [ Placeholder content for popup link ] WordPress Download Manager - Best Download Management Plugin