nagle / delayed ack in default tcp wan optimized profile

the issue with nagle and delayed acks interaction is well known and documented, F5 themselves reference to it in an article:

so why has the default tcp-wan-optimized profile both nagle and delayed acks enabled? does anyone use this default profile, does it work for you or not?

Ha, good question - I have asked myself the same thing. Glad you brought it up. I don’t use that profile though, so can’t give you any feedback on its effect.