Closed (outdated)
Project:
Drupal core
Version:
6.x-dev
Component:
cron system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
25 Oct 2010 at 07:26 UTC
Updated:
2 Mar 2016 at 22:18 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
swentel commentedTrue, that one can actually go.
Comment #2
gordon commentedThis could also be backported to Drupal 6.x as well sometime.
Comment #3
moshe weitzman commentedComment #4
dries commentedCommitted to CVS HEAD. Moving to D6.
Comment #5
swentel commentedD6 patch
Comment #6
andypostThere's reason to cleanup this on cron within system and filter module both.
Comment #7
gábor hojtsyI'm a bit hesitant on this actually. Does it mean any measurable performance improvement? (Notice we are changing the API by removing a function that was not really intended to be invoked directly but somebody might have done so).
Comment #9
andypostI think this function could be safely removed because it's just a code cleanup.
I think if someone use a core hook implementation for any reasons - this eay is wrong.
The performance improvement could be visible only on highload systems because of time-frame between two cleanups (system & filter) module). Anyway this is a -1 within "delete query" so hook_cron could run a bit faster
Comment #10
gábor hojtsyLooking for more feedback.
Comment #11
gábor hojtsyMaybe we will get some more feedback this way?
Comment #12
gordon commentedThis is really just to a clean up and to remove a duplicate process, as clearing the filter cache twice is not going to clear out the filter cache anymore than it 1 clear cache process is going to do.
It is not a performance improvement but getting rid of some code rot.
Gordon.