> > What if the content is dynamically generated?
>
> Then send normal? It just seems like a lot of CPU to be compressing the
> same content over and over.
Profile, don't speculate.
The bottleneck is often not the server CPU or disk, but the end user's
connection - usually 56Kbps or less. In such cases, it may be much
better to compress a dynamically-generated entity while sending it.
Compressing the data has two other benefits that apply even if the end
user has a fast connection: you send fewer packets, and you send less
total data. Fewer packets means fewer possible dropped packets, and
dropped packets can be a big performance hit. Less total data usually
means lower cost. For example, I pay $35/GB of data I upload on my T1.
