This message was deleted.

Yep still using the XAXD profile - if you run the wizard even on the very latest 13.x build out of the box it still enables the XAXD profile too. It would be great if they gave some justification as to why the default TCP profile is now preferred...

I found a article where they started don't use angle anymore. I opened a ticket because I need answers

Following, I'd love to see a definitive answer as well. I've been running a custom XA_XD profile at most customers for a few years already with no negative (but also no clear positive ) feedback. The support article makes me want to cry though: we'd advise some different setting on netscaler gateway implementations, so lets go ahead and change the default tcp profile and unbind any tcp profile from gateway so we're sure it's taking the default ... I mean... seriously?

yea, I got conformation finally. Nagle needs to be turned off. The support guy stated, it will be updated in future releases. So I turned it off for the XA_XD profile for now. I didnt set the default on the Gateway side, because I need to understand and compare the settings and differences.

Nice, thx for the confirmation. Went back to look in my mails and I did also confirm it with a Citrite NS guru before implementing it seems about 2 years ago. I do see for example that in 12.1 firmwares they have increased a lot of values as opposed to 2 years ago when I took a clone of the default XA_XD profile and made a custom one with nagle off and the buffer size increases. So they are clearly changing them still in firmwares, really sad that they don't disable nagle then and keep the default profile up to date with the best general settings.