gifdrop
gifdrop copied to clipboard
Caching for main image query
The main image query grabs a lot of data. Might see if storing this in postmeta will help it scale.
maybe a transient?
Could be a lot of data for the options table. Will have to see what, say, 2k images does. We are going to have other scaling issues too.
can we pare down the query itself?
or random idea: store the query results as a JSON file and then pull that?