Skip to content

Conversation

@Chrissi2812
Copy link

Summary of Changes

Added Basic Profiling for Plugins in Joomla. Just like we already have for modules and components.

One Problem is that something is happening after the afterExecutePlugin Joomla\CMS\Service\Provider\Session::session.start that takes some time that isn't profiled correctly for now. Because of that the beforeExecutePlugin right after the session.start can be a bit misleading. But at least we have a basic understanding of which plugins slow down a page.

image

Testing Instructions

  1. Enable Debugging and Profiling
  2. Load a Page and look for beforeExecutePlugin afterExecutePlugin

Documentation Changes Required

Co-authored-by: Harald Leithner <leithner@itronic.at>
@laoneo
Copy link

laoneo commented Jan 27, 2025

This is a framework package, we shouldn't add here a dependency to the CMS classes. What happens when a project uses this package and declares the JDEBUG constant?

@HLeithner
Copy link

True sorry didn't noticed the repo when commenting the constant. I see no option to jnclude this into this package.

@laoneo
Copy link

laoneo commented Jan 27, 2025

Pretty sure there is a way to do this in the dispatcher service provider.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants