custom field - Best Practice for storing aggregate data by date or other criteria?

admin管理员组

文章数量:1125072

I'm creating summary descriptions by year. To do this I do update_post_meta on save to set values for word count, image count, external link count.

So for a year archive page I iterate over each post to create sums and then format the result.

With caching I can be sure to serve cached results to the users.

But during development with caching on I do notice the slowness.

I was considering using a cron like mechanism to create the HTML summaries in a subdirectory of the wp-content folder or as wp_object_cache items with a names like summary-YYYY.html for the summary or summary-YYYY.json.

My question:

What are my options for storing data like these? Are there any best practices for naming keys in the object cache? Are there other ways to associate arbitrary data with a year?

I'm creating summary descriptions by year. To do this I do update_post_meta on save to set values for word count, image count, external link count.

So for a year archive page I iterate over each post to create sums and then format the result.

With caching I can be sure to serve cached results to the users.

But during development with caching on I do notice the slowness.

I was considering using a cron like mechanism to create the HTML summaries in a subdirectory of the wp-content folder or as wp_object_cache items with a names like summary-YYYY.html for the summary or summary-YYYY.json.

My question:

What are my options for storing data like these? Are there any best practices for naming keys in the object cache? Are there other ways to associate arbitrary data with a year?

• custom-field
• cache
• date
• meta-value

Share Improve this question edited Mar 3, 2024 at 9:16 fuxia♦ 107k3838 gold badges255255 silver badges459459 bronze badges asked Mar 2, 2024 at 19:21 artlungartlung 3,09766 gold badges2929 silver badges3737 bronze badges

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 0

I settled on using wp_cache_set and wp_cache_get which seems to do well. I create a key based on the class, function, and parameters:

$cacheKey = self::createCacheKey( __CLASS__, __FUNCTION__, $referenceYear, $referenceMonth );

createCacheKey() looks like:

protected static function createCacheKey( ...$args ): string {
    return implode('-', $args);
}

And I'm sure to use an appropriate expiration. For dates that are not this year or month I have longer expirations set.

Getting and returning the cache looks like this at the top of a function:

    $cacheKey = self::createCacheKey( __CLASS__,
                                      __FUNCTION__,
                                      $referenceYear, 
                                      $referenceMonth );
    $cache    = wp_cache_get( $cacheKey, self::CACHE_GROUP );
    if ( $cache ) {
        return $cache;
    }

And at the end of those functions I use:

    wp_cache_set( $cacheKey, $output, 
                  self::CACHE_GROUP, $cacheExpiration );

This seems like it's doing what I want and improves performance though it appears the default place things are stored and how reliable this is depends on server configuration.

本文标签： custom fieldBest Practice for storing aggregate data by date or other criteria