Nokron
WAF F5
NokronGitLabELK stackWAF F5
WAF F5
NokronGitLabELK stackWAF F5
  • BIG-IP Application Security Manager
    • HTTP Protocol
      • Deep Dive to “HTTP Request” on ASM Module
      • ASM Example: Detecting a Malicious HTTP Request
    • Introduction to OWASP Top-10 Security Risks
    • Application Security Policy Templates in F5 ASM
      • Security Policy Levels
      • Explicit Entities Learning
      • Policy Modification
      • Gradual / Modular Blocking
      • Application Security Policy Lifecycle
      • Security Policy Enforcement Modes
      • Security Policy Violation Flags
      • How to Increase Learning Score / Deployment Speed
      • Comparison: Enforcement Mode, Learning Mode, and Violation Flags
    • Security Entities in Application Security Policy
      • Enforcement Readiness Summary
      • HTTP / HTTPS / WS / WSS URLs
      • Allowed Parameters in Security Policies
      • Allowed File Types in Security Policies
    • Tuning Security Policies: Analyzing and Categorizing Violations
      • Learning Suggestions in Security Policy Tuning
      • Policy Diff: Comparing and Auditing Security Policies
    • IP Address Exception Properties in ASM/AWAF
    • Cross-Site Request Forgery (CSRF) Protection in F5 ASM/AWAF
    • Sensitive Data Masking / Scrubbing (Data Guard) in F5 ASM/AWAF
    • Anti-virus Protection through an ICAP Server in F5 ASM/AWAF
    • Cookies in F5 ASM/AWAF Security
    • Session Tracking and Session Awareness in F5 ASM/AWAF
    • Evasion Technique Detection in F5 ASM/AWAF
    • Important Tips about Security Policy in F5 ASM/AWAF
    • L7 DDoS Attack Protection Configuration
    • TPS-based Attack Vectors and Stress-based Attack Vectors
    • Mitigation Techniques for DoS and Bot Protection
    • Important Tips about Events Logging
    • High-Speed Logging (HSL) Configuration
    • Web Threat Campaigns (v14.0+)
    • IP Intelligence (IPI) Subscription-Based License
    • Geo-IP Database Functionality
    • General Security Standards and WAF Support
    • ASM - Virtual Edition (VE) Tips
    • How to Bypass ASM Module
    • ASM Traffic Processing Daemon (bd)
    • ASM and AAM Integration
  • BIG-IP LTM Technology
    • Source IP Address and PORT Translation in BIG-IP
    • Packet Filters
    • Traffic / Service Profiles in BIG-IP
    • Virtual Servers and Their Behavior with Different Profiles in BIG-IP
      • Detailed Overview of Profiles in BIG-IP LTM
      • Optimizing for Mobile Clients in BIG-IP LTM
      • Connection Mirroring in BIG-IP LTM
      • AVR (Analytics) Profile in BIG-IP LTM
      • Health Monitoring in BIG-IP LTM
      • SSL Profile in BIG-IP LTM
      • Load-balancing Methods in BIG-IP LTM
      • Persistence Profile in BIG-IP
      • CMP vs. SMP in BIG-IP Systems
      • OneConnect Profile in BIG-IP
Powered by GitBook
On this page
  1. BIG-IP LTM Technology
  2. Virtual Servers and Their Behavior with Different Profiles in BIG-IP

CMP vs. SMP in BIG-IP Systems

BIG-IP systems utilize both Symmetric Multi-Processing (SMP) and Clustered Multi-Processing (CMP) architectures for processing tasks efficiently. Below is a comparison and explanation of how each works:

Symmetric Multi-Processing (SMP)

  • Overview:

    • SMP spreads multiple threads across multiple processors in a system.

    • A single TMM (Traffic Management Microkernel) instance runs, with its threads distributed to utilize all available cores.

  • Key Characteristics:

    • Threads operate within a single process.

    • Shared memory space is used for communication between threads.

    • Suitable for smaller workloads or when the overall system load is not highly distributed.

Clustered Multi-Processing (CMP)

  • Overview:

    • CMP provides a separate instance of the TMM process on each CPU core.

    • Connections are distributed among the available TMM processes.

    • Each TMM operates independently, applying load-balancing algorithms separately within its scope.

  • Key Characteristics:

    • Better suited for highly parallel workloads.

    • Independent memory spaces for each TMM process eliminate contention and locking overhead.

    • More scalable for environments with high concurrency and traffic distribution needs.

  • Limitations:

    • Virtual Editions (VE):

      • CMP is supported but does not utilize Hyper-Threading (HT) split technology.

      • VE instances are limited by the virtual CPU cores allocated by the hypervisor.

  • Benefits:

    • Enhanced performance by distributing workloads more evenly across cores.

    • Greater fault isolation between processes.

Comparison Table

Feature

SMP

CMP

Architecture

Single TMM instance with multiple threads.

Multiple independent TMM instances (one per core).

Memory

Shared memory space.

Independent memory spaces.

Load Distribution

Threads are spread across processors.

Connections are distributed among TMM processes.

Scalability

Limited by thread contention.

Scales better for high parallelism.

Fault Isolation

Single point of failure.

Fault isolation between TMM processes.

Best Use Case

Smaller workloads or less distributed loads.

High-concurrency or high-traffic environments.

Recommendation

  • Use CMP when deploying BIG-IP in environments with multiple cores and high-performance requirements.

  • SMP might be sufficient for smaller or less demanding environments but may not utilize hardware as efficiently as CMP.

PreviousPersistence Profile in BIG-IPNextOneConnect Profile in BIG-IP

Last updated 3 months ago