Forum Discussion
Impact of reducing TMM memory allocation
I've currently got my tmm memory allocation set to the default value
sys db tmm.proxyssl.cachesize { default-value "2621440" scf-config "true" value "2621440" value-range "unsigned integer min:0 max:18446744073709551615"
I've recently had issues with my device where tmm memory hits 95% causing aggressisive disconnections in order to reduce memory usage. I'm looking to reduce the mem allocation, but not sure what is an acceptable value or how to determine a value acceptable for my device in relation to current operations.
Is there a way of determining an acceptable value? also what will be the impact if I just reduced the value to about 1.7G?
2 Replies
- Laudec
Nimbostratus
Are you certain your device is not facing a DoS attack perhaps? High memory utilization could indicate a DoS attack, and F5 reaping connections to mitigate it.
- AceVenturer_278
Nimbostratus
Doesn'nt look like a DoS attack, I think the default setting was the issue. After confirming with F5 support on the value proposed we reduced the capacity and we are working fine.
Thanks
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)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