Feature #687
Make Page Caching a viable option for stripped down sites
| Status : | Closed | Start : | ||
| Priority : | Normal | Due date : | ||
| Assigned to : | pdcawley - | % Done : | 0% |
|
| Category : | frontend | |||
| Target version : | 5.1 | |||
| Resolution : | fixed |
Description
I recently upgraded the development version of typo, and the page caching no longer works. Considering this is the reason I use typo, its a pretty big bug, IMHO. Quick check in the source code shows that it was completly removed.
Overall its a huge performance hit. In a properly configured lighttpd-fcgi environment performance goes from 1000req/sec to 80req/sec, and for users in a CGI shared hosting environment they will max out somewhere around 10-15req/sec maximum.
Although moving to action caching DOES enable more features, the option of page caching would be really nice for people who can live without those features.
Is removal of this feature a sign that people should start using MovableType or will the option to use page caching be re-added in the near future?
History
03/29/2006 06:17 PM - pdcawley -
- Status changed from New to Assigned
If you look in articles_controller you'll see that it suggests replacing 'caches_action' with 'caches_page' in that file. I don't know how tested it is, but I don't think we've done anything to break it yet.
We will revisit this issue I'm sure, but probably not before 4.0.
What I'd like to do is to be able to have a blog option that says "Turn page caching on for this blog" and then only get offered a restricted set of sidebars which work in a page cached environment, and warnings when you try to post an article with a publication date in the future, etc.
I'm marking this as an enhancement rather than a defect and pushing it into the 4.1 milestone -- I really want it, but I want to get 4.0 out the door more.
03/29/2006 06:49 PM - scott -
In a CGI environment, you'll be getting 5-10 requests/*minute* at best...