Entries very slow to save; many specific Low Reorder sets the issue?
EE 2.5.3, Low Reorder 2.1.1.
We have about 48 custom reorder sets, almost all of which deal with a specific channel. Each set is searching on two custom fields and a category. Saving entries in this channel is incredibly slow now, and though I haven't currently proven that it's due to Low Reorder, it is using entry_submission_end. There are a couple other add-ons using that same hook, but this slowness wasn't apparent until I built so many Reorder sets.
Is there any way to narrow this down for sure to know that it is Low Reorder causing this, and if it is, can we find a way to delay, speed up, or eliminate it using entry_submission_end? Is there a hook even after that for example? Re-do the sets with a cron job? Index the low_reorder tables? (Thinking out loud here...) Thanks!
Replies
Low 7 Mar 2013 09:19
So do all 48 sets target the same channel?
You could disable the Low_reorder_ext/entry_submission_end row in the exp_extensions table by setting enabled to 'n'. If you do, new entries will not be automatically added to their sets, but you'd have to re-save each set relevant for that entry.
Ryan 7 Mar 2013 15:30
Yeah, almost every one of those reorder sets targets the same channel. I was trying to save the editors any extra steps as far as getting their content in the right order on the correct pages - seems like having to have them go to the set to refresh it defeats that point. We'll keep brainstorming here.
Low 7 Mar 2013 15:41
How many entries are there in that channel, approximately? I'd like to try and stress test this, so I need to get as close as your case as I can.
Ryan 7 Mar 2013 15:42
We're leaning towards doing what you're doing in the entry_submission_end hook, but on a cron job running every few minutes, not when an entry is saved. Any thoughts or warnings about that?
Low 7 Mar 2013 15:44
Well, you'll need to send along the entry's ID, channel ID possible selected category IDs.
If you're running a cron job, I'm not sure how you can target the specific entry that was edited...?
Low 8 Mar 2013 10:05
I've found a way to vastly improve the entry_submission_end routine. Will add it to the next version and I can send you a patched file, if you'd like.
Low 12 Mar 2013 08:07
Should be fixed in 2.1.2!