+1  A: 

Identify parts of your Web content that is static, potentially most popular, large (for instance animations, images). These are usually the parts you should consider first.

Here you can find excellent Caching Tutorial

mloskot
Tutorial's about client-side caching mostly, but thanks anyway.
MInner
You didn't specify what caching you mean exactly, but OK.
mloskot
A: 

One thing to analyze is if the information in your pages needs to be always up to date or if you could delay the updates holding them in a cache for period of time. This dependes on the kind of site.
There are some real big sites that reaches to the point of having inconsistent data for a while until all cache nodes are updated.

rodrigoap
and what if it's a kind of Wiki? Memcache'll probobly die out? And perfomance of memcache will be lower than simple mysql query, isn't it? (on a few millions records)
MInner
A: 

Caching makes sense if and only if you have some (spatial, temporal) locality, such as the most frequent queries (temporal locality). If you have a model where each page is fetched with uniform probability, then caching is a complete nonsense, yes.

akappa