Download & Extend
Issues

Implement a locking framework and make caching pluggable

Posted by Damien Tournoud on January 14, 2009 at 10:26am
Project:Drupal core
Version:7.x-dev
Component:base system
Category:task
Priority:normal
Assigned:Unassigned
Status:closed (duplicate)

Issue Summary

This is a spin-off of #251792: Implement a locking framework for long operations for D7 only.

The issue is still the same: when a cache entry expire and need to be regenerated (think locale cache, menu cache, etc.), several regeneration can occur in parallel because we currently have no locking. This hurts badly websites that sustain high request rates, especially in cluster environments.

The D7 implementation will be very different from the D6 one:

  • The system will comply to our new pluggable paradigms.
  • We will strongly link caching and locking. This make sense because we are generally locking to prepare a cached object: if using an APC cache for example, that is local to each web node, we don't need to lock the whole cluster.
  • We will have a new (probably fluent) API.
Login or register to post comments

Comments

#1

Posted by kbahey on January 14, 2009 at 4:46pm

Thanks Damien. Subscribing.

#2

Posted by moshe weitzman on January 20, 2009 at 3:18pm

Subscribe as well

#3

Posted by birdmanx35 on January 25, 2009 at 4:16am
Status:active» postponed

Perhaps we should wait for #363787: Plugins: Swappable subsystems for core?

#4

Posted by moshe weitzman on January 25, 2009 at 4:21am
Status:postponed» active

We should not postpone in favor of extremely early stage patches that are only slightly related. We have substantial issues here that need review beyond just the mechanics of how we make something pluggable. The only answer to that question in terms of this issue is"we make pluggable using the standard practice in core" which is not handlers right now.

Also, please do not change status with a msg like "perhaps".

#5

Posted by Jeremy on January 28, 2009 at 10:10pm

Subscribing.

#6

Posted by michtoen on January 30, 2009 at 3:43pm

+1

#7

Posted by slantview on February 18, 2009 at 5:31am

This issue seems to be idling a bit. what do we need to push this forward, and is it too late for D7 already?

#8

Posted by CorniI on April 19, 2009 at 9:44am

subscribe, I'd like to see and review how you implement the locking mechanism :)

#9

Posted by coltrane on July 29, 2009 at 5:30pm

#251792: Implement a locking framework for long operations has a patch for D7 as RTBC, is this issue here still needed?

#10

Posted by Damien Tournoud on July 30, 2009 at 10:52pm
Status:active» closed (duplicate)

Yep, let's close that.