Forum Discussion
How is CPU/Memory shared across Virtual Servers?
Hello,
Using TMOS on HW as a reference point TMOS uses/assigns CPU to TMM process for consistent performance using features likes Hyper Threading etc. TMOS does use adaptive resource allocation based on traffic patterns etc. While TMOS memory is shared across all session and connections served by the TMOS the VS would consume more or less based on its current load.
BIG-IP will allocate more resources on the more heavily used VS however resources are not infinite ☹️, there are a number of mechanisms and features deployed to protect the system:
For DDoS you really should consider Distributed Cloud DDoS Protection
If you don't have a DDoS at the very least, you should consider provisioning BIG-IP Advanced Firewall Manager | F5 to deal with/manage against many different DoS vectors.
BIG-IP system wise uses adaptive reaping to protect the system under duress and possible DoS scenarios: Overview of adaptive connection reaping (11.6.0 and later)
TCP/UDP profiles can manage and protect against buffer resource exhaustion, keepalives etc.
Managing Traffic with Bandwidth Controllers & Managing Traffic with Rate Shaping are features that can help protect against large traffic spikes
You can also limit the number of connections on the Virtual Server, Pool Member and or Node: Setting Connection Limits
These are just a few things that come to mind, I didn't even mention iRules would open the door for other mitigations as well.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com