Sergey Biryukov

Creates a separate tiny .mo file to use on a site front-end. Allows to save some amount of RAM on a shared hosting server.
Thanks to MAX for the original non-plugin solution and to AlexPTS for the idea.

WPLANG Lite

Creates a separate tiny .mo file to use on a site front-end.

berkux

WP-Memory-Usage is a lightweight but powerful WordPress plugin that monitors and displays memory usage directly in your WordPress admin area. 
It is essential for site administrators and developers who need to keep an eye on memory consumption, identify bottlenecks, and act before users are affected.
What the plugin shows:
In the admin footer (every admin page): 
* Current memory usage vs. WordPress limit (with percentage) 
* Current memory usage vs. PHP limit (with percentage) 
* Server IP address and server name 
* PHP version
In the Dashboard widget (“Memory Overview”): 
* PHP version, architecture (32/64 bit), max execution time 
* WordPress memory limit (WP_MEMORY_LIMIT), WordPress admin limit (WP_MAX_MEMORY_LIMIT), PHP memory limit 
* Current peak memory usage with a visual progress bar (colour-coded: green / orange / red) 
* Latest digest status summary (warn / danger / critical badges) 
* Link to the Threshold Alerts settings page
Settings & Monitor — Tabs (since 2.0.0):
<ul>
<li>Settings — thresholds, logging options, email alerts, log rotation</li>
<li>History — latest logged requests with full context (URL, type, user, memory)</li>
<li>Digest — aggregated summaries of past log intervals; browse, merge, and delete digest files</li>
<li>️Actions — practical guidance on what to do when you receive a memory alert</li>
<li>Diagnose (new in 2.1.0) — full PHP/WordPress configuration snapshot with a ready-to-paste AI prompt for analysis</li>
<li>Memory Thresholds — current limits, threshold assessment, and recommendations</li>
<li>Check Installation — verifies that the plugin can run correctly on your server</li>
</ul>
<h3>Why Use WP-Memory-Usage?</h3>
Excessive memory usage leads to slower sites, HTTP 500 errors, and failed background jobs (cron, imports, backups). WP-Memory-Usage gives you the information you need to act before users are affected — without overwhelming you with notifications.
<h3>Features</h3>
<ul>
<li>Real-time memory display in the dashboard widget and every admin page footer</li>
<li>Colour-coded progress bar (green / orange / red) for instant status recognition</li>
<li>Three alert levels: Warning, Danger, Critical — each configurable as a percentage of the effective memory limit</li>
<li>Flexible logging: Ajax, REST, Admin, Cron, favicon requests — log only what matters</li>
<li>Email alerts with configurable recipient</li>
<li>History tab: recent requests with full context (URL, type, admin screen, REST route, AJAX action, user)</li>
<li>Digest tab: aggregated interval reports — browse, merge, and delete digest files</li>
<li>Actions tab: plain-language guidance on resolving memory alerts, no developer skills required</li>
<li>Diagnose tab (new in 2.1.0): full configuration snapshot + one-click AI prompt (English, copy & paste ready)</li>
<li>Memory Thresholds tab: shows effective limits, threshold gaps, and concrete recommendations</li>
<li>Check Installation tab: verifies log directory, WP-Cron, PHP functions, disk space, and email setup</li>
<li>Admin bar indicator: quick status badge visible on every admin page</li>
<li>Multisite compatible</li>
<li>Clean uninstall: removes all options, cron jobs, database-tables and log files on deletion</li>
</ul>
<h3>PluginCheck-Plugin Status</h3>
Plugin is compatible with PluginCheck-Plugin. Note regarding “trademarked_term”: “WP-Memory-Usage” and “wp-memory-usage” are today considered restricted terms. This plugin entered the WordPress repository in 2009, when those terms were permitted.
<h3>Credits</h3>
Copyright 2009–2013 by Alex Rabe, 2022– Bernhard Kux

WP-Memory-Usage

Monitor PHP memory usage, set alert thresholds, and diagnose your server configuration — directly inside WordPress admin.

WPLANG Lite vs WP-Memory-Usage