Thanks for the quick replies Chris & John!
I’ll have a think about the problem from another angle, specifically looking at CPTs.
Fortunately the project is still relatively young and I’m in a position where I can change approach relatively easily.
I was hoping that while there will likely be be a large number of rows, the data would be basic enough for this not to be an issue overall when using save_post.
I know this topic is years old but I was just wondering whether anyone had found any solutions to this?
I’m currently using WordPress/ACF for a digital treasure trail PWA/webapp. I have a global ‘Scores’ repeater on an options page that adds a new row (with 16 basic number or text fields) each time a player completes a trail.
At present the Options page/repeater has about 450 rows and it’s becoming really slow when executing save_post.
