kanti/server-timing

Show timings of Database and HTTP Calls

1.1.1 2023-01-17 16:38 UTC

Requires

• php: ~7.4 || ~8.0 || ~8.1 || ~8.2
• composer-runtime-api: ^2.0.0
• ocramius/package-versions: ^2.1
• typo3/cms-core: 10.* || 11.* || 12.*
• typo3/cms-extbase: 10.* || 11.* || 12.*

Requires (Dev)

• infection/infection: ^0.18.2 || ^0.26.13
• phpstan/extension-installer: ^1.1
• phpunit/phpunit: ^9.5
• pluswerk/grumphp-config: ^4.0 || ^5.0
• saschaegerer/phpstan-typo3: ^1.1
• typo3/cms-adminpanel: 10.* || 11.* || 12.*

GPL-2.0-or-later

• Matthias Vogel

README

installation

composer require kanti/server-timing

at the moment there is nothing to configure

Server timings are not displayed in production for users who are not logged into the backend.

Included measurements:

• php: from start of php call to the register shutdown function
• middleware: will show how much time was spend in the inward and outward middleware directions
• sql: shows the sql query's
• extbase: show all Extbase dispatches, (forwards are included in the original action call)
• guzzle: external API calls are measured if they use the official TYPO3 RequestFactory or the GuzzleClientFactory)

if a measurement key has more than 4 entries, they will get combined into one total time with a count. And the 3 longest entries will be kept

Measure your own timings:

stopWatch function (recommended)

  $stop = \Kanti\ServerTiming\Utility\TimingUtility::stopWatch('doSomething', 'additinal Information');
  $result = $this->doSomethingExpensive();
  $stop();

start & stop functions

this has some limitations, there can only be one doSomething at a time.

  \Kanti\ServerTiming\Utility\TimingUtility::start('doSomething', 'additinal Information');
  $result = $this->doSomethingExpensive();
  \Kanti\ServerTiming\Utility\TimingUtility::end('doSomething');

TODO List:

todos:

• more tests

composer patches needed?

• fluid renderings (possible solution with XClasses?)

wanted:

• functional tests

nice to have?

• ViewHelpers