This link has been bookmarked by 151 people and liked by 1 people. It was first bookmarked on 06 Feb 2008, by Royce Guin.
-
10 Jul 15
-
19 Jan 12
-
06 Jan 12
-
28 Jul 11
-
15 Jul 11
-
15 Jun 11
-
04 Jun 11
-
01 Jun 11
-
01 Mar 11
-
02 Feb 11
dilterportoHttpModules
-
20 Nov 10
-
10 Nov 10
-
03 Oct 10
-
02 Oct 10
-
20 Aug 10
-
18 Aug 10
-
30 Jul 10
-
04 Jun 10
-
27 Apr 10
-
30 Mar 10
-
10 Mar 10
-
27 Feb 10
-
09 Feb 10
-
11 Dec 09
-
24 Oct 09
-
27 Aug 09
-
13 Jun 09
-
04 Apr 09
-
27 Mar 09
-
21 Mar 09
-
03 Mar 09
-
23 Feb 09
Sean Patterson10 easy ways to make ASP.NET and AJAX websites faster, more scalable and support more traffic at lower cost; Author: Omar Al Zabir; Section: ASP.NET; Chapter: Web Development
-
06 Feb 09
-
28 Dec 08
-
12 Dec 08
-
-
there are secret bottlenecks in Membership and Profile provider
-
there are secret bottlenecks in Membership and Profile provider which can be solved easily to make authentication and authorization faster
-
HTTP pipeline can be tweaked to avoid executing unnecessary code
-
Worker Process can be pushed to its limit to squeeze out every drop of performance out of it
-
Page fragment output caching on the browser
-
On demand UI loading
-
Content Delivery Networks (CDN)
-
HTTP Cache headers
-
remove these default modules from your Web application by adding
<remove>nodes in your site's web.config -
he process model configuration can be tweaked to make ASP.NET process consume more system resources and provide better scalability
-
there'll be 40 threads allocated for ASP.NET. This means at a time ASP.NET can process 40 requests in parallel on a dual core server
-
If you have an application which is not that CPU intensive and can easily take in more requests per second, then you can increase this value
-
if your Web application uses a lot of Web service calls or downloads/uploads a lot of data which does not put pressure on the CPU
-
On a dual core computer, there'll be 40 threads allocated for ASP.NET for I/O operations. This means at a time ASP.NET can process 40 I/O requests in parallel on a dual core server
-
Especially when your Web application downloads/uploads data, calls many external webservices in parallel
-
you can set this value to a low number in order to increase the number of concurrent requests
-
you can set this to a lower value than
minWorkerThreadsbecause there's no issue of parallel processing in case of I/O threads -
If you have only your Web application running in a dedicated box and there's no other process that needs RAM, you can set a high value like 80
-
Sites that fetch external content a lot suffer from congestion due to the default setting. Here I have set it to
100 -
it can also cache XML HTTP calls if the call is a HTTP
GET -
If you return the
Expiresheader during the response, the browser will cache the XML HTTP response. There are two headers that you need to return with the response that instruct the browser to cache the response -
As long as you make the same XML HTTP call with the same parameters, you will get cached response from the compute
-
SetCacheability
-
SetExpires
-
SetMaxAge
-
AppendCacheExtension
-
There's a bug in ASP.NET 2.0 that you cannot change the
max-ageheader. Asmax-ageis set to0, ASP.NET 2.0 sets theCache-controlto private becausemax-age = 0means no cache is needed. So, there's no way you can make ASP.NET 2.0 return proper headers which cache the response. This is due to the ASP.NET AJAX Framework that intercepts calls to Webservices and incorrectly sets themax-ageto0by default before executing a request -
using Reflection
-
Response from the new URL can also be cached in the browser if you return proper caching headers
-
One common mistake is to sometimes omit the “www” subdomain from the URL. www.pageflakes.com/default.aspx is not same as pageflakes.com/default.aspx. Both will be cached separately
-
If you update a file which was cached by
Expiresheader, new users will immediately get the new file while old users will see the old content until it expires on their browser. So, as long as you are usingExpiresheader to cache static files, you should use as high a value as possible. -
As a result, it does not help setting a lower value assuming all users will pick up the latest file soon. You will have to change the URL of the file in order to ensure everyone gets the exact same file immediately.
-
-
03 Dec 08
-
03 Oct 08
-
30 Sep 08
-
12 Sep 08
-
06 Sep 08
-
04 Sep 08
-
31 Aug 08
-
30 Jul 08
-
29 Jul 08
-
28 Jul 08
-
15 Jul 08
-
07 Jul 08
-
25 Jun 08
-
11 Jun 08
-
06 Jun 08
-
28 May 08
-
25 May 08
-
31 Mar 08
-
11 Mar 08
-
05 Mar 08
-
26 Feb 08
-
22 Feb 08
-
15 Feb 08
-
14 Feb 08
-
12 Feb 08
-
11 Feb 08
-
08 Feb 08
-
06 Feb 08
-
Chris van LeeuwenThings You Must Do for ASP.NET Before Going Live
ASP.NET configuration performance optimization scalability for:lathain for:jbok
-
05 Feb 08
Mark Pawelek10 easy ways to make ASP.NET and AJAX websites faster, more scalable and support more traffic at lower cost; Author: Omar Al Zabir; Section: ASP.NET; Chapter: Web Development
-
04 Feb 08
-
03 Feb 08
-
02 Feb 08
-
01 Feb 08
-
-
31 Jan 08
-
noneya bidnez10 Great ASP.NET performance tips
asp.net performance optimization scalability .net development
-
30 Jan 08
-
01 Dec 07
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.