Title: Memory Scan Ìtumọ̀ Yorùbá: – PHP Memory Usage Ìtumọ̀ Yorùbá: – No Crash Author: Service2Client LLC Published: Agẹmọ 14, 2026 Last modified: Agẹmọ 16, 2026 --- Ṣàwárí àwọn plugin ![](https://ps.w.org/memory-scan/assets/banner-772x250.jpg?rev=3608084) ![](https://ps.w.org/memory-scan/assets/icon-256x256.png?rev=3608084) # Memory Scan Ìtumọ̀ Yorùbá: – PHP Memory Usage Ìtumọ̀ Yorùbá: – No Crash Láti ọwọ́ [Service2Client LLC](https://profiles.wordpress.org/service2client/) [Ṣe ìgbàsílẹ̀](https://downloads.wordpress.org/plugin/memory-scan.1.1.0.zip) * [Àwọn àlàyé](https://yor.wordpress.org/plugins/memory-scan/#description) * [Àwọn àgbéyẹ̀wò](https://yor.wordpress.org/plugins/memory-scan/#reviews) * [Ìgbéwọlẹ̀](https://yor.wordpress.org/plugins/memory-scan/#installation) * [Ìdàgbàsókè](https://yor.wordpress.org/plugins/memory-scan/#developers) [Ìrànlọ́wọ́](https://wordpress.org/support/plugin/memory-scan/) ## Àpèjúwe Memory Scan tells you, in plain terms, whether your WordPress site has enough PHP memory to run reliably — and warns you _before_ a low-memory crash instead of after. It also keeps an eye on two things that quietly take sites down: running an end- of-life PHP version, and upgrading PHP before your plugins are ready. Rather than guessing from a single admin page (which is one of the lightest requests on a site), Memory Scan records the real peak memory of each request type — front- end, admin, AJAX and cron — and judges your headroom against your PHP `memory_limit` with a built-in safety margin. **What you get:** * **Real measured headroom** — based on the heaviest actual request seen, not a synthetic number. * **Three at-a-glance metrics** — current headroom, recommended-for-your-site-type, and real peak by request — that escalate from “YouÌtumọ̀ Yorùbá: ’re fine” to“ Urgent” as memory gets tight. * **Per-plugin expected-peak ranking** so you can see which plugins (page builders, SEO suites) demand the most memory. This figure is a deliberately conservative estimate, not a live measurement — WordPress cannot bill runtime memory to a single plugin — so it errs high to keep your site safe. * **A recommended `memory_limit`** for your detected site type (simple blog, Elementor, WooCommerce, or a heavy stack). * **A proactive warning** that appears on every admin page when memory is low — so you are told without hunting for it. * **A `WP_MEMORY_LIMIT` check** that flags when it is set below your PHP `memory_limit`, with the exact `wp-config.php` line to fix it. * **A Dashboard widget** — an at-a-glance memory status on your main dashboard, so you can see the plugin is watching without any nag. * **A PHP version support check** — tells you whether the PHP version your server runs still receives security patches, and when it reaches end of life, based on php.netÌtumọ̀ Yorùbá: ’s published schedule. * **A PHP 8.x plugin-readiness check** — compares your active plugins against WordPress. orgÌtumọ̀ Yorùbá: ’s own published data (declared PHP requirement, WordPress “ tested up to,” and last-updated date) and flags which look ready, which to verify, and which are high-risk before you move PHP up. It reads published data — it does **not** run your plugins — so a green result is a strong signal, not a guarantee, and premium or custom plugins that are not in the WordPress.org directory are shown as “could not verify.” * **Site Health integration** — the PHP-support and memory verdicts also appear under Tools Site Health, where hosts and experienced admins look. Memory Scan is read-only with respect to your content: it never changes your posts, pages, or other plugins’ settings. It only reads memory figures and writes its own small diagnostic values. It never changes your PHP version either — it detects and advises; your host controls the PHP version. ## Àwọn àwòrán ìbòjú [⌊The Memory Scan overview: current headroom, recommended memory for your site type, and the escalation banner.⌉⌊The Memory Scan overview: current headroom, recommended memory for your site type, and the escalation banner.⌉[ The Memory Scan overview: current headroom, recommended memory for your site type, and the escalation banner. [⌊Real peak by request type and the per-plugin expected-peak ranking.⌉⌊Real peak by request type and the per-plugin expected-peak ranking.⌉[ Real peak by request type and the per-plugin expected-peak ranking. [⌊PHP version support status and the PHP 8.x plugin-readiness check.⌉⌊PHP version support status and the PHP 8.x plugin-readiness check.⌉[ PHP version support status and the PHP 8.x plugin-readiness check. [⌊The Memory Scan verdicts surfaced under Tools ](https://ps.w.org/memory-scan/assets/screenshot-4.PNG?rev=3609545) The Memory Scan verdicts surfaced under Tools Site Health. ## Ìgbéwọlẹ̀ 1. Upload the `memory-scan` folder to `/wp-content/plugins/`, or install it through the Plugins screen in WordPress. 2. Activate the plugin through the **Plugins** screen. 3. On first activation youÌtumọ̀ Yorùbá: ’ll be taken to the Memory Scan page. After that you can open it any time from the **Memory Scan** menu. 4. Browse a few pages and run your heaviest task so it can record real peaks, then reload the scan. ## FAQ ### Does this slow my site down? No. It records the memory peak at the end of each request (a couple of arithmetic operations), and only performs the heavier per-plugin scan on admin requests, cached hourly. Nothing extra runs on front-end page loads beyond recording a single number. ### Is the per-plugin “expected peak” an exact measurement? No, and it says so on screen. PHP cannot attribute runtime memory to an individual plugin from a single request, so the per-plugin figure is a conservative estimate based on each pluginÌtumọ̀ Yorùbá: ’s code size. It errs high on purpose, so you provision enough memory rather than too little. The overall verdict uses your real measured peak. ### Does the PHP compatibility check run my plugins? No. It reads WordPress.orgÌtumọ̀ Yorùbá: ’s published data about each plugin — the declared PHP requirement, the WordPress “tested up to” version, and the last-updated date, the same information shown on each pluginÌtumọ̀ Yorùbá: ’s page. It never executes your plugin code, so it is safe, but a green result is a strong signal rather than a guarantee. The only certain test is running the upgrade on staging. ### Does the compatibility check call an external server or slow my site? It looks plugins up on WordPress.org — the same service WordPress already uses to check for plugin updates. Those lookups happen only when you click the “Check compatibility” button on the Memory Scan page, are limited to a handful at a time, time out quickly, and are cached for a week. Nothing runs on your visitors’ pages, and if WordPress. org is slow or unreachable the plugin simply shows “could not verify” rather than waiting. ### Why do some plugins show “not in the WordPress.org directory”? Premium plugins and custom-built plugins are not hosted in the WordPress.org directory, so there is no published data to read. Those are shown as “could not verify” — check the developerÌtumọ̀ Yorùbá: ’s own PHP-compatibility information for them. ### It says my WP_MEMORY_LIMIT is below my PHP memory_limit. What do I do? The plugin shows the exact line to add to `wp-config.php`. That setting lives outside any plugin, so Memory Scan can only detect and advise, not change it for you. ### Does it change or delete any of my content, or change my PHP version? No. Memory Scan is read-only with respect to your content — it never touches posts, pages, or other plugins’ settings, and it never changes your PHP version. It only detects and advises. ## Àwọn àgbéyẹ̀wò Kò sí àwọn àgbéyẹ̀wò fún plugin yìí. ## Àwọn Olùkópa & Olùgbéejáde “Memory Scan Ìtumọ̀ Yorùbá: – PHP Memory Usage Ìtumọ̀ Yorùbá: – No Crash” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí plugin yìí. Àwọn Olùkópa * [ Service2Client LLC ](https://profiles.wordpress.org/service2client/) [Túmọ̀ “Memory Scan Ìtumọ̀ Yorùbá: – PHP Memory Usage Ìtumọ̀ Yorùbá: – No Crash” sí èdè rẹ.](https://translate.wordpress.org/projects/wp-plugins/memory-scan) ### Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè? [Ṣàwárí koodu](https://plugins.trac.wordpress.org/browser/memory-scan/), ṣàyẹ̀wò [ibi ìpamọ́ SVN](https://plugins.svn.wordpress.org/memory-scan/), tàbí ṣe àgbékalẹ̀ sí [àkọsílẹ̀ ìdàgbàsókè](https://plugins.trac.wordpress.org/log/memory-scan/) nípasẹ̀ [RSS](https://plugins.trac.wordpress.org/log/memory-scan/?limit=100&mode=stop_on_copy&format=rss). ## Àkọsílẹ̀ àwọn àyípadà #### 1.1.0 * New: Dashboard widget showing an at-a-glance memory status. * New: PHP version support / end-of-life advisory on the Memory Scan page, based on php.netÌtumọ̀ Yorùbá: ’s published schedule. * New: PHP 8.x plugin-readiness check using WordPress.org published data (declared PHP requirement, “tested up to,” and last-updated), with bounded, cached, opt- in lookups that never block a page. * New: Site Health integration — the PHP-support and memory verdicts now also appear under Tools Site Health. * New: Menu icon and a logo at the top of the Memory Scan page. * Improved: Clearer first-run and low-memory messaging. #### 1.0.1 * Maintenance and text fixes. #### 1.0.0 * Initial release. ## Àkójọpọ̀ Meta * Ẹ̀yà **1.1.0** * Ìgbàgbọ́hùn tó kẹ́yìn **ọjọ́ 6 sẹ́yìn** * Àwọn ìgbéwọlẹ̀ tó ṣiṣẹ́ **Tó kéré sí 10** * Ẹ̀yà WordPress ** 5.0 tàbí ju bẹ́ẹ̀ lọ ** * Dánwò dé **7.0.2** * Ẹ̀yà PHP ** 7.0 tàbí ju bẹ́ẹ̀ lọ ** * Èdè * [English (US)](https://wordpress.org/plugins/memory-scan/) * Àwọn àmì * [memory](https://yor.wordpress.org/plugins/tags/memory/)[memory limit](https://yor.wordpress.org/plugins/tags/memory-limit/) [performance](https://yor.wordpress.org/plugins/tags/performance/)[php compatibility](https://yor.wordpress.org/plugins/tags/php-compatibility/) [site health](https://yor.wordpress.org/plugins/tags/site-health/) * [Ìwòye Tó Péye](https://yor.wordpress.org/plugins/memory-scan/advanced/) ## Àwọn ìbò Kò sí ìwádìí tí a tíì fi ránṣẹ́. [Your review](https://wordpress.org/support/plugin/memory-scan/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/memory-scan/reviews/) ## Àwọn Olùkópa * [ Service2Client LLC ](https://profiles.wordpress.org/service2client/) ## Ìrànlọ́wọ́ Nǹkan wà tí o fẹ́ sọ? Ṣé o nílò ìrànlọ́wọ́? [Wo àpéjọ ìrànlọ́wọ́](https://wordpress.org/support/plugin/memory-scan/) ## Ṣe ìtọrẹ Ṣé o fẹ́ ṣe àtìlẹ́yìn fún ìlọsíwájú plugin yìí? [ Ṣe ìtọrẹ sí plugin yìí ](https://www.service2client.com/dynamic-post-donation)