Caching versus <a href="http://www.setgetweb.com/p/WAS51/portal/IWWCM/doc/pre-renderedsites.html">Pre-rendering</a>

Caching versus Pre-rendering

A Pre-rendered Web Content Management Site can be viewed in two ways:

Via a HTTP server Viewing a Pre-rendered site via a HTTP server is similar to using Basic Caching as the displayed Content is static and Custom Caching cannot be used.
Via Web Content Management Viewing a Pre-rendered site via the Web Content Management application is similar to using Advanced Caching as Content can be dynamic and Custom Caching can be used.

Basic Caching versus a Pre-rendered Site delivered via a HTTP server

At first glance, the Pre-rendering feature and Basic Caching do the same thing. There are however, some major differences that will determine which feature is the best for you.
The main difference between the two features is that Web Content Management's Pre-rendering feature takes a "snap-shot" of the entire Site each time it is run. Basic Caching only caches on a "page by page" basis. If performance is your main issue, then Pre-rendering may be the answer. If not, then Basic may be a better option.

Basic Caching Pre-rendered Site delivered via a HTTP server
Performance Very fast Extremely fast
"Connect" tags processing No No
Custom Caching No No
Memory Requirements Low to Medium. Memory requirements depends on the web server being used.
Disk Requirements Low to Medium. Potentially very high as the entire site must be able to fit on disk.
Unexpected Broken Links Yes
As some pages may be cached at different times, there is a small chance that not all the links on a cached page may be currently valid.
No
The Site is Pre-rendered in a single "batch", greatly reducing the chances of inconsistencies in the Site.

Advanced Caching versus a Pre-rendered Site delivered via Web Content Management

These options are very similar. You may have to test both strategies before deciding which is best for your Site.

Advanced Caching Pre-rendered Site delivered via Web Content Management
Performance Fast when cached, but slower if the requested page has expired from the cache. (As tag processing has a cost, this depends on how many "Connect" tags a page contains.) Fast, but as tag processing has a cost, this depends on how many "Connect" tags a page contains.
"Connect" tag processing Yes Yes
Custom Caching Yes Yes
Memory Requirements Medium to high. Medium to high.
Disk Requirements Medium to high. Medium to high.
Unexpected Broken Links Yes
As some pages may be cached at different times, there is a small chance that not all the links on a cached page may be currently valid.
No
The Site is Pre-rendered in a single "batch", greatly reducing the chances of inconsistencies in the Site.

Parent topic: Caching Options.
IBM Workplace Web Content Management - V5.1.0.1 -

Workplace Web Content Management is a trademark of the IBM Corporation in the United States, other countries, or both.

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.

Via a HTTP server	Viewing a Pre-rendered site via a HTTP server is similar to using Basic Caching as the displayed Content is static and Custom Caching cannot be used.
Via Web Content Management	Viewing a Pre-rendered site via the Web Content Management application is similar to using Advanced Caching as Content can be dynamic and Custom Caching can be used.

	Basic Caching	Pre-rendered Site delivered via a HTTP server
Performance	Very fast	Extremely fast
"Connect" tags processing	No	No
Custom Caching	No	No
Memory Requirements	Low to Medium.	Memory requirements depends on the web server being used.
Disk Requirements	Low to Medium.	Potentially very high as the entire site must be able to fit on disk.
Unexpected Broken Links	Yes As some pages may be cached at different times, there is a small chance that not all the links on a cached page may be currently valid.	No The Site is Pre-rendered in a single "batch", greatly reducing the chances of inconsistencies in the Site.

	Advanced Caching	Pre-rendered Site delivered via Web Content Management
Performance	Fast when cached, but slower if the requested page has expired from the cache. (As tag processing has a cost, this depends on how many "Connect" tags a page contains.)	Fast, but as tag processing has a cost, this depends on how many "Connect" tags a page contains.
"Connect" tag processing	Yes	Yes
Custom Caching	Yes	Yes
Memory Requirements	Medium to high.	Medium to high.
Disk Requirements	Medium to high.	Medium to high.
Unexpected Broken Links	Yes As some pages may be cached at different times, there is a small chance that not all the links on a cached page may be currently valid.	No The Site is Pre-rendered in a single "batch", greatly reducing the chances of inconsistencies in the Site.