[wp-hackers] compression and caching

[Dion Hulse (dd32)]

On Sun, 27 Dec 2009 15:31:52 +1100, Micah <wp at twolanedesign.com> wrote:

>>> But it made me wonder why compression and caching isn't included in the
>> core.
>>
>> These require a well-configured server, hence why WordPress leaves it  
>> to a
>> combination of plugins and, frankly, a well-configured server.
>
> I could see this argument stand if compression was ongoing, on the fly,  
> or
> in large amounts. Compression doesn't and shouldn't happen continuously,  
> and
> cached files are stored and served up as needed. In theory, compression
> actually saves CPU load, reduces http/php request sizes and would save
> bandwidth handled by a server.

You need to seperate Compression and Caching here.

Compression does not reduce CPU Load, Caching does.

There are Many *good* caching plugins for WordPress, But none of them can  
deal with a often changing Dynamic website AFAIK, And none of them belong  
in core in my opinion as they're better suited to running as plugins.

WordPress removed Compression in 2.5 as it was a buggy function, It didnt  
work on some servers due to double-compression, and some users couldnt  
understand that. In addition, It didnt do caching, so it would increase  
server load and subsequently, load times.








-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/