The rate will be about 8k req/s, whereas currently graphite1001
receives about 350k metric updates per second, so we would expect
this to increase statsd load by about 2%.
This would have been very helpful in diagnosing API cluster overload
incidents such as the one on July 11.
Change-Id: I0a248e1bcec05915d98ec735f4cfb9800e64412d
$this->executeAction();
$runTime = microtime( true ) - $t;
$this->logRequest( $runTime );
$this->executeAction();
$runTime = microtime( true ) - $t;
$this->logRequest( $runTime );
- if ( $this->mModule->isWriteMode() && $this->getRequest()->wasPosted() ) {
- MediaWikiServices::getInstance()->getStatsdDataFactory()->timing(
- 'api.' . $this->mModule->getModuleName() . '.executeTiming', 1000 * $runTime
- );
- }
+ MediaWikiServices::getInstance()->getStatsdDataFactory()->timing(
+ 'api.' . $this->mModule->getModuleName() . '.executeTiming', 1000 * $runTime
+ );
} catch ( Exception $e ) {
$this->handleException( $e );
$this->logRequest( microtime( true ) - $t, $e );
} catch ( Exception $e ) {
$this->handleException( $e );
$this->logRequest( microtime( true ) - $t, $e );