Profiler v1.0.4
- Seller MojoRisin
- Creation date
Stop guessing which addon is slow.
Time-bounded profiler that attributes every request, query, template, and cron to the addon that caused it.
Overview Copyright info Releases (1)
Blatchy Profiler
Stop bisecting your addons to find the slow one. Start a sampling cycle, reproduce the slowness, and see exactly which addon is responsible.
What it does
How to run it
Why you'd use it
Attribution
Requests are attributed by the controller class namespace that handled them. Vendor/Addon-namespaced classes map cleanly to their add-on. Core classes are attributed to XF. When one addon extends another's controller, the attribution follows whichever class actually ran.
Permissions
Access is gated by a dedicated admin permission (Resource profiler). Super admins have it by default.
Privacy
No external calls. Everything stays on your server. Sampling is off by default — you start it explicitly when you want to profile.
Note on busy sites
While a cycle is active, every sampled request writes rows to the profiler tables. On high-traffic sites that can mean hundreds of MB of data during a single cycle. The 2-cycle cap resets this on each new start, but be mindful if you have tight disk space.
Requirements
XenForo 2.3+
Stop bisecting your addons to find the slow one. Start a sampling cycle, reproduce the slowness, and see exactly which addon is responsible.
What it does
- Samples requests, template renders, cron jobs, and slow queries (>=20ms) and attributes them to the add-on that caused them
- Dashboard rollup shows per-addon request counts and total, DB, template, and cron time
- "Slowest individual requests" table lets you drill into any page load
- Drilldown shows the page's slow queries (with duration) and template renders (with count)
- Auto-stops after 15 minutes so it never runs forever
- Keeps the last 2 cycles only — older data is automatically discarded
How to run it
- Install the addon.
- Go to Admin CP → Logs → Resource profiler.
- Click Start sampling. A new cycle begins and auto-stops after 15 minutes (or click Stop sampling anytime).
- In another tab, reproduce the slowness — load the page, click the link, run the action you suspect.
- Return to the dashboard and refresh. Click any request to drill into its slow queries and templates.
- Export any table to CSV if you want to share or archive it.
Why you'd use it
- Your site got slow and you have 20+ addons installed
- A specific page feels sluggish and you want to know why
- You suspect an addon is firing too many queries but don't know which one
- You want to compare before/after a change without deploying a full APM stack
Attribution
Requests are attributed by the controller class namespace that handled them. Vendor/Addon-namespaced classes map cleanly to their add-on. Core classes are attributed to XF. When one addon extends another's controller, the attribution follows whichever class actually ran.
Permissions
Access is gated by a dedicated admin permission (Resource profiler). Super admins have it by default.
Privacy
No external calls. Everything stays on your server. Sampling is off by default — you start it explicitly when you want to profile.
Note on busy sites
While a cycle is active, every sampled request writes rows to the profiler tables. On high-traffic sites that can mean hundreds of MB of data during a single cycle. The 2-cycle cap resets this on each new start, but be mindful if you have tight disk space.
Requirements
XenForo 2.3+