Back to Community
Home / Community / Plugin → Duplicate post

Understanding and Responding to Duplicate Post Performance Logs

24 threads Sep 9, 2025 Plugin → Duplicate post

Content

If you use the Duplicate Post plugin, you may have encountered a message asking you to share your "copy logs." This can be confusing if you weren't experiencing an obvious problem. This guide explains what these logs are, why the plugin collects them, and what the data means for your WordPress site.

What Are Duplicate Post Copy Logs?

The Duplicate Post plugin includes a diagnostic feature that runs every time you clone a post, page, or custom post type. This feature generates a small log entry that records key performance metrics from your server during the duplication process. The data is anonymized and is designed to help developers understand how the plugin performs across a wide range of hosting environments.

What Information is in the Logs?

When you are prompted to share logs, the data typically includes three main sections:

  • Server Environment: Details about your server's operating system (usually Linux), PHP version, WordPress version, and MySQL version.
  • Copy Logs: A list of timestamps for each copy operation with performance data:
    • Total/Avg Time: How long the duplication process took in seconds. Lower numbers (e.g., 0.03s) indicate faster performance.
    • Memory Usage (mem): The amount of memory the WordPress process was using when the copy was made.
    • Peak Memory (peak): The highest amount of memory used during the process.

Why Was I Asked to Share These Logs?

Based on community reports, the plugin will request this data for two primary reasons:

  1. Performance Optimization: The plugin detected a duplication event that was slower than average or used more server resources than typical. The developers use this data to identify performance bottlenecks.
  2. Bug Investigation: If a user reports a specific bug (like in Thread 24, where taxonomies weren't copying in a Multisite setup), the logs provide crucial context about the server environment where the error occurred.

Should I Be Worried About My Site's Performance?

In most cases, no. A single slower copy operation does not necessarily indicate a problem with your site. Many factors can cause a temporary spike, such as high server load at that moment. However, consistently high times or memory usage across multiple logs could point to an underlying issue worth investigating.

Common Solutions and Best Practices

If you are concerned about your duplication performance, here are the most common steps to improve it:

  1. Check Your PHP Version: Many logs show sites running older PHP versions (7.3, 7.4). Upgrading to a supported version of PHP (8.0 or higher) can significantly improve the performance of all your plugins, including Duplicate Post.
  2. Review Your Hosting Environment: Consistently high execution times (e.g., over 1 second as seen in Thread 24) can indicate underpowered hosting. Consider reviewing your hosting plan if your site has grown in complexity.
  3. Manage Your Post Content:
    4. Posts with a large number of revisions, custom fields, or complex metadata will naturally take longer to copy. Regularly cleaning up old post revisions can help.
  4. Conflict Testing: A sudden change in performance could be caused by a conflict with another plugin or your theme. To test for this, temporarily switch to a default WordPress theme (like Twenty Twenty-Four) and disable other plugins one by one to see if duplication speed improves.

By sharing your logs, you contribute valuable data that helps the Duplicate Post team make the plugin faster and more reliable for everyone. It is a collaborative process that benefits the entire WordPress community.

Related Support Threads Support