For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

mike_afonso_107's avatar
mike_afonso_107
Icon for Nimbostratus rankNimbostratus
Aug 29, 2007

speeding up WEB Applications

Folks ...   i have recently ran into an issue where application administrators have been complaining about the speed of their .NET applications opening when connecting through the LTM. If they con...
config
design
James_Thomson's avatar
James_Thomson
Icon for Employee rankEmployee
Sep 04, 2007
I have seen instances where adding persistence helps speed up a site because only one application instance is being hit per user. Although, in your case, you had source addr persistence already enabled. The HTTP profile's job is to enforce proper HTTP data as it flows through the BIG-IP. I have seen instances where applications were broken when not going through BIG-IP, but then fixed when going through BIG-IP becuase of something like the browser not support HTTP 1.1 and the server expecting it. The BIG-IP does HTTP 1.1 transformations where it can change 1.0 requests to 1.1 requests on the backend. So, the HTTP profile is doing a lot of things to streamline HTTP connections to the backend.

 

Did you change the TCP profile in the Virtual Server when you made this change as well? Are you using any other acceleration features like caching, compression or WebAccelerator? They might help accelerate more in the future.