Ticket #624 (closed defect: wontfix)

Opened 2 months ago

Last modified 2 months ago

Object Cache: Should be a core function in MU, not just via API.

Reported by: lunabyte Assigned to: somebody
Priority: high Milestone:
Component: component1 Version:
Severity: major Keywords: object cache, 1.5
Cc:

Description

Been a subject of great debate recently, and it's now getting attention here:

http://mu.wordpress.org/forums/topic.php?id=8169

Having object cache as a plugin on a WP install makes sense. It's one site, and usually not hit enough to be that big of a problem.

Enter MU, and serving tons of blogs. Every little bit helps, and object cache was definitely helping more than hurting. Yes, there have been a few issues with it, but they can be fixed (widget updating, post/page save and continue editing, etc).

With MU it just doesn't make sense to dump it as a plugin. The file is already there, and it makes more sense to have it in the core so that there is one less file include.

Change History

05/09/08 13:34:53 changed by lunabyte

  • keywords set to object cache, 1.5.
  • priority changed from normal to high.
  • severity changed from normal to major.

05/12/08 11:04:56 changed by donncha

  • status changed from new to closed.
  • resolution set to wontfix.

Sorry, won't happen, but I will update the README file with links to the common object cache plugins.

Unfortunately the file cache (which is the most common one) doesn't work on all hosts and causes performance problems on other hosts, especially those that use NFS mounted drives.