amic Front-End Heartbeat Cont
| 开发者 | |
|---|---|
| 更新时间 | 2025年12月7日 14:44 |
| PHP版本: | 7.2 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Some caching plugins offer manual heartbeat control. For best results, allow this plugin to manage your heartbeat intervals automatically. You do not need to configure a manual frequency in any other plugin—feel free to use their other features, but avoid enabling their manual heartbeat settings.
- Verified GDPR compliance: the plugin does not collect or store any personal data.
- Rigorously tested to ensure reliable performance during high-traffic surges.
安装:
- Upload the plugin from WordPress or extract it inside the "/wp-content/plugins/" directory.
- Activate the plugin from the Plugins menu in the WordPress admin dashboard.
- You can access the plugin’s features and settings under Settings > DFEHC in the WordPress admin.
常见问题:
How is this different from setting a manual frequency?
A manual heartbeat frequency is a fixed value chosen to fit your general usage scenario. However, this static setting isn’t always ideal for every front-end visitor at the moment they access your site, which can result in longer and unnecessary load times. With a dynamic heartbeat frequency, your website can consistently operate at optimal performance. This is especially valuable for sites in highly competitive niches where every metric affects search rankings, ad performance, and even hosting costs. A real-time adaptive frequency ensures each visitor receives the most efficient heartbeat interval, reducing response times, improving page load speed, and minimizing unnecessary server load.
How do I configure the plugin on my website?
The plugin automatically delivers the most optimal heartbeat frequency by analyzing your hosting environment, website size, and real usage patterns. In most cases, no user intervention is required after activation. You can access Settings → DFEHC in the WordPress admin to view available configuration options, such as setting a manual heartbeat frequency or disabling the heartbeat entirely. For advanced users working on specific or unusual projects, the plugin also provides several filters that allow fine-tuning and precise control over the heartbeat pace.
I have existing performance and SEO optimization plugins. Will this plugin cause any conflicts?
Not at all. This plugin is built to enhance your website’s performance and is fully compatible with all major performance and SEO tools. The only potential overlap is that some of these plugins may include an option to set a manual heartbeat frequency. This is the only area where settings can compete. Even if both are enabled, your website will not crash. However, to ensure the heartbeat frequency remains dynamically managed, avoid enabling or configuring manual heartbeat frequency settings in other caching or performance plugins while using this plugin.
更新日志:
- Improved cron scheduling.
- Redeclared dfehc_server_load_ttl adjustment.
- General enhancements.
- Improved multisite support.
- Increased resilience and reliability under high-traffic loads and limited server resources.
- Enhanced overall compatibility and security.
- Applied final tune-ups for seamless continuity in the upcoming branch; the current plugin version is performing at its best to date. The plugin was subjected to rigorous stress tests—far beyond the traffic levels most websites will ever face.
- Plugin update recommended to benefit from these improvements.
- Improved code quality and structure.
- Added self-healing spike load calibration and enhanced resilience under high concurrency.
- Comprehensive under-the-hood overhaul.
- General enhancements.
- Improved database health and load estimation logic.
- Improved filtering and average calculation accuracy.
- Reduced JS overhead.
- Added additional safety guards.
- Minor updates on optimization features.
- Minor improvements on compatibility for the upcoming major update.
- Added database optimization feature on the DFEHC settings page to help with database bloat and unoptimized or dead-end tables.
- Minor improvements.
- Improved server load and response time retrieval functions to address potential issues on certain hosting environments where the functions might get blocked. Thanks to user Tom M for notifing this isssue.
- Efficiency improvements.
- Performance improvements and bug fixes.
- Localized chart.js file
- Settings page update.
- Code structure upgrade.
- Added the ability to manually control back-end heartbeat as well as editor heartbeat intervals.
- Now you can adjust the resource priority from WP Admin Dashboard > Settings > DFEHC
- Efficiency improvements.
- Enhanced Unix server load detection.
- Added a new setting in the plugin's settings DFEHC page that allows users to completely disable the WordPress Heartbeat API.
- Efficiency improvements.
- Improved object caching calling method.
- Other small code and visual adjustments.
- Added Heartbeat Health widget in the admin dashboard.
- Performance & security improvements.
- Small code improvements.
- Persistent Storage Support: Added support for Redis and Memcached as persistent storage options for efficient data handling and improved performance.
- Settings Page: Added a dedicated settings page to configure Redis and Memcached settings, providing flexibility in specifying server and port information. In the event the user does not have persistent storage support options, the plugin will fallback to regular caching. Update the settings only if they are needed from your WP Admin dashboard > Settings > DFEHC
- Improved Load-Based Recommendations: Calculate the recommended heartbeat interval based on server load average and response time to optimize performance
- Made various updates to improve compatibility with different server configurations and enhance overall performance.
- Improvements in error reporting.
- Reliability improvements.
- Implemented an asynchronous heartbeat determination feature, ensuring that the plugin operates seamlessly within any WordPress setup without compromising performance. By offloading the heartbeat calculation to a separate asynchronous process, the plugin remains non-invasive and minimizes any potential impact on the overall performance of your website.
- Small corrections and code minification.
- Fixed compatibility issues with some older versions of server-side programs.
- Minor corrections.
- Performance improvements.
- The plugin has undergone extensive improvements to ensure seamless integration and optimal performance across various WordPress configurations. With its new enhanced compatibility, it can seamlessly adapt to different themes, plugins, and hosting environments, providing a reliable solution for all types of WordPress websites.
- Added more complex reasoning behind determing the best recommended heartbeat inteval.
- Set the grounds for easier future updates.
- Added a new way of calculating heartbeat accuracy.
- Improved compatibility with shared hosting environments where users have no control over the server load.
- Hearbeat is now taken into account on pages that can only be accesible to visitors.
- Now caching the frequently used DOM elements to avoid unnecessary reselection and improve performance.
- Various realiability improvements.
- Updated heartbeat structure to incorporate heartbeat caching. Recommended heartbeat caching will automatically be disabled when it doesn't make sense anymore. For example the website is crowded.