Re: Performance Problems with Probing
From: Jeffrey Tan[MSFT] (v-jetan_at_online.microsoft.com)
Date: 08/23/04
- Next message: Jakob Christensen: "RE: String Literal"
- Previous message: Jon Skeet [C# MVP]: "Re: Deadlock - Not Responding"
- In reply to: Jediah L.: "Re: Performance Problems with Probing"
- Next in thread: Jediah L.: "Re: Performance Problems with Probing"
- Reply: Jediah L.: "Re: Performance Problems with Probing"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 23 Aug 2004 08:25:02 GMT
Hi Jediah,
Sorry for letting you wait for so long time.
=====================================
1. Based on my understanding, your #1 requirement is disabling the
anonymous authentication to improve your Asp.net application performance.
First, this requirement can only be done at server side, because you can
not force all the client customer browser(IE) to do anything. But again,
this http authentication request can only be controlled at client IE side,
because IE always send anonymous request, then with windows account
information. This indicates that this requirement can not be controlled.(As
I originally said, you can not control million client's browser setting)
Second, the key performance issue of Asp.net Application is server side
code parsing, Html code rendering and Html code client parsing, but not the
HTTP request, so you may pay more attention to improve the application
performance. For more information about improving Asp.net performance,
please refer to:
"Improving ASP.NET Performance"
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/
scalenetchapt06.asp
Third, NTLM authentication is a complex authentication, which involves
several HTTP request and authentication information exchange. And the first
anonymous http request time can be ignored comparing with the NTLM
authentication.
2. I think it is the same as the first question
3. First, you may check IIS setting's "HTTP headers" tabpage, if you set
"Enable Content Expiration" with "Expiration Immediately".
Second, using the siffer, you may check, if the IIS reponse has "no-cache"
http header.
Third, I think the problem may be on your specific IE side. You may do some
test to confirm this:
Does your problem machine request other server pages?
Does other machine's IE also has this problem?
==================================================
Thank you for your patience and cooperation. If you have any questions or
concerns, please feel free to post it in the group. I am standing by to be
of assistance.
Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
- Next message: Jakob Christensen: "RE: String Literal"
- Previous message: Jon Skeet [C# MVP]: "Re: Deadlock - Not Responding"
- In reply to: Jediah L.: "Re: Performance Problems with Probing"
- Next in thread: Jediah L.: "Re: Performance Problems with Probing"
- Reply: Jediah L.: "Re: Performance Problems with Probing"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|