Not sure if anyone cares about D5 anymore. But I was doing some PHP profiling and I discovered a few opportunities for improvement with the actions module, for all I know these have long been fixed so take-it-or-leave-it:

- created a registry of action functions. I think the way I've set this up it will only regenerate when a new module is installed or something else happens that wipes {cache_menu} .

- (Un)Publishing a node used to use node_save(). This really adds a lot of load because chances are that this is being called when the given node is already being saved. By switching to a simple query we save a lot but loose anything that would fire on that normally. This was definitely worth it in my point of view.

CommentFileSizeAuthor
actions_caching.diff1.47 KBdalin

Comments

pomliane’s picture

Status: Active » Closed (won't fix)

This version of Actions is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.

This issue has been automagically closed by a script.