Closed (duplicate)
Project:
Drupal core
Version:
7.x-dev
Component:
base system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
14 Jan 2009 at 10:26 UTC
Updated:
30 Jul 2009 at 22:52 UTC
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:
Comments
Comment #1
kbahey commentedThanks Damien. Subscribing.
Comment #2
moshe weitzman commentedSubscribe as well
Comment #3
birdmanx35 commentedPerhaps we should wait for #363787: Plugins: Swappable subsystems for core?
Comment #4
moshe weitzman commentedWe 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".
Comment #5
jeremy commentedSubscribing.
Comment #6
michtoen commented+1
Comment #7
slantview commentedThis issue seems to be idling a bit. what do we need to push this forward, and is it too late for D7 already?
Comment #8
CorniI commentedsubscribe, I'd like to see and review how you implement the locking mechanism :)
Comment #9
coltrane#251792: Implement a locking framework for long operations has a patch for D7 as RTBC, is this issue here still needed?
Comment #10
damien tournoud commentedYep, let's close that.