Kbase 21441: How to Employ Caching to Improve WebSpeed Performance
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/15/2008 |
|
Status: Verified
GOAL:
How to employ Windows client-side caching to improve performance for WebSpeed applications running on IIS.
GOAL:
What options in IIS can be tuned for webspeed?
GOAL:
How to configure IIS to improve webspeed performance?
FACT(s) (Environment):
WebSpeed 3.x
Windows 32 Intel
Windows NT 32 Intel/Windows 2000
IIS 5.0
IIS 5.1
FIX:
Given here is a brief outline of the cache control options available on Windows platforms.
-- Server-side caching [IIS (v5 for this example)] can be set with
cache control headers for the image files.
1) Look in - Internet Service Manager
2) Right click the Web site and choose "Properties". The "Web Site
Properties" file comes up
3) Go to the "HTTP Headers" tab and use the "Enable Content
Expiration" configuration and "Custom HTTP Headers" to set
caching parameters
**Additional reference materials listed below provide further
details.
-- Client-side caching - Check the browser settings
1) Under Internet Explorer 5+ look under: "Tools" menu, "Internet
Options"
2) Select the "General" tab
3) Click on the "Settings" button for "Temporary Internet Files"
Radio buttons here allow different options for cache-control.
They are:
- Every Visit to the page -
Will always download, ignoring Server-side caching headers.
- Every time you start Internet Explorer -
Will download once per session.
- Automatically -
Uses cache control rules
(Expiry headers, If-Modified-Since, etc.)
- Never -
Always use cached version, never checking for new versions.
If caching is disabled on either the Server or Client-side of a WebSpeed application, each request to the Server will send another copy of each file involved in the request.
Fortunately, it is possible to check for the existence of content which already exists on the Client and thus avoid unnecessary downloads.
Image files, as mentioned above, are good candidates for caching because they are typically larger and slower to load. The time saved in the download process thereby speeds up your application's performance