Closed (fixed)
Project:
Authenticated User Page Caching (Authcache)
Version:
6.x-1.0-rc1
Component:
Documentation
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
4 Feb 2010 at 20:25 UTC
Updated:
4 Feb 2010 at 22:59 UTC
Comments
Comment #1
Jonah Ellison commentedIf Drupal core caching is enabled, then the 50:1 is a fairly accurate statement. Page load time, however, is ultimately dependent on how complex your site is (e.g., how many modules are installed, how many Views you are using, how powerful your host is, etc). The Drupal page cache is cleared on a fairly regular basis (such as when the cronjob is run), especially for more community-oriented websites (such as when a comment is made).
What Drupal core does not offer is caching for authenticated users, which is what this module achieves. If you are creating a specific role in which each of these users receives a nearly identical page, then Authcache can be implemented fairly easily. These logged-in users would then be able to receive cached pages as fast as an anonymous user would!
Comment #2
jponch commentedThanks! So just to clarify, if my site is having users of a specific role viewing the exact same content (ex. a page with some text and a few images), then that 50:1 ratio can be knocked down to 1:1 via authcache? If so that's awesome!
Comment #3
Jonah Ellison commentedYes -- though it may be more like 2:1 or 3:1, since Authcache requires a lightweight Ajax phase for logged-in users. The page load time will definitely be similar to a cached anonymous page.
Comment #4
jponch commentedhey, even 3:1 is an amazing improvement over 50:1! Thanks. Marking as closed - question answered.