Edit report at https://bugs.php.net/bug.php?id=55526&edit=1
ID: 55526 Updated by: f...@php.net Reported by: adrien at antipoul dot fr Summary: Heartbeat rate too high causes a lot of events -Status: Assigned +Status: Analyzed Type: Feature/Change Request Package: FPM related Operating System: Linux PHP Version: 5.3.8 Assigned To: fat Block user comment: N Private report: N New Comment: In fact the FPM heartbeat should be disabled if request_terminate_timeout and request_slowlog_timeout are not set on all pools. And if they are, the heartbeat frequency should be generated dynamically. A patch is coming (no ETA yet) Previous Comments: ------------------------------------------------------------------------ [2011-08-29 08:22:25] f...@php.net The FPM heartbeat is used to check timeouts on its children which includes: - request_terminate_timeout - request_slowlog_timeout If you don't use those features, the heartbeat is useless as it does nothing. If you use those features, you can higher the heartbeat frequency accordingly. If you need to change it quickly, you can edit the source file fpm_process_ctl.h and change /* 130ms heartbeat for pctl */ #define FPM_PCTL_HEARTBEAT (130) to what you want. ------------------------------------------------------------------------ [2011-08-28 16:59:07] adrien at antipoul dot fr Description: ------------ Hi, It seems that FPM has a heartbeat each 130ms. This is really short, and make php-fpm the #1 event generator on my personal server, that also runs Apache, NGinx, dovecot, powerdns, NSD3 and unicorn. There might be a good reason for such a heartbeat, but there also might be a way to at least increase it to 5 or 10 seconds. I'll be glad to help and get rid of this, as soon as I understand what this heartbeat is helpful for. ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=55526&edit=1
