F5 VM Sizing

Hi,

So what f5 are trying to give you is a rough idea of how much through the appliance can take,

Not on the left the size of server that's used and the notes about the NIC used all important when trying to compare like for like.

What I was trying to say is this is rule of thumb here, and you need to go in with some assumption which you need to validate.

So bandwidth and connections per second are key.

Bandwidth gives you a limit due to licensing.

Connections per second is key but is benched against the performance of the server or virtual configuration you are using.

If connection go up, the resource of the box will go up, as it start to saturate the server your performance will drop. This is then easily to fix in the first instance, up the virtual cores or memory to give more resources. This should then lower the latency again of your traffic and get you operating again.

So like server management and performance management in general monitoring and visibility is key to understanding what you are dealing with.

The the realistic approach of you can design to you are sick of doing it and getting the approvals but the moment the system is turned on your calculations go out of the window as you now have live data to benchmark this on.

So really the question is, have you got bandwidth and connectivity info from your app teams which you can overlay onto the f5 data?