Optimize kwata kwata — kwata kowane yana sha lodi kafin ya gaji ga na gaba. Burin shine a bada saura bubuwan daga cache kuma lissafin da namebase ba shi da shi yi aiki kamar hakan.
Umowa pool-din zuwa RAM ɗinka, kuma bada damar don PHP a sanya sa lokaci ɗaya, ba a kowane bubar ba:
; php-fpm pool: cap workers so you don't exhaust RAM
; pm.max_children = (available RAM for PHP) / (avg process size, ~50MB)
pm = dynamic
pm.max_children = 40 ; hard ceiling on concurrent PHP workers
pm.start_servers = 10
pm.min_spare_servers = 8
pm.max_spare_servers = 16
pm.max_requests = 500 ; recycle workers to avoid memory leaks
; OPcache: cache compiled bytecode in memory
opcache.enable = 1
opcache.memory_consumption = 256
opcache.max_accelerated_files = 20000
opcache.validate_timestamps = 0 ; skip file-stat checks in prod (flush on deploy)
Jin max_children ya kasanta sosai ka badi kuma ka fadi; kasa kuma bubuwan suna jeniya (502s karkatar).
Wannan tsarin tunani yana nufin tunatarhin shafi na gida zai iya komawa daga gefuna ko cache na shafi ba tare da taɓa PHP ko DB kwata-kwata ba.
Bada damar slow query log don samun masu laifi, ƙara indexes don ƴan ƙaddamar, da bincika autoloaded options (wp_options tare da autoload = yes a loda akan kowa bubar — tilas dadi autoload data ya daina koyi-koyi duka). A ƙarshe, rage bakin plugin: plugin kowa ya ƙara bubuwan kuma aiki PHP, don haka cire waɗanda ba a amfani su ba.
Bubar WordPress yana da nauyi PHP- da DB ta al'ada, don haka ba ta bugi karkatar ba tare da ƙananta. Tsarin bakin cache (OPcache → object cache → page cache → CDN) kuma daidai-daidai PHP-FPM da bakin database ya bada wato watari ɗaya hankali iya hada da zafi kamar yadda — kuma ya lissafe shi a jiya na ƴan tsayi.