public function PurgerCapacityDataInterface::getIdealConditionsLimit in Purge 8.3
Get the maximum number of invalidations that this purger can process.
When Drupal requests are served through a webserver, several resource limitations - such as maximum execution time - affect how much objects are given to your purger plugin. However, under certain conditions - such as when ran through the command line - these limitations aren't in place. This is the 'ideal conditions' scenario under which your purger can operate.
However, we cannot feed the entire queue at once and therefore there will always be a hard outer limit of how many invalidation objects are being processed during Drupal's request lifetime.
Return value
int The number of invalidations you can process under ideal conditions.
See also
\Drupal\purge\Plugin\Purge\Purger\CapacityTrackerInterface::getRemainingInvalidationsLimit()
1 method overrides PurgerCapacityDataInterface::getIdealConditionsLimit()
- PurgerBase::getIdealConditionsLimit in src/
Plugin/ Purge/ Purger/ PurgerBase.php - Get the maximum number of invalidations that this purger can process.
File
- src/
Plugin/ Purge/ Purger/ PurgerCapacityDataInterface.php, line 47
Class
- PurgerCapacityDataInterface
- Describes what capacity tracking expects from purger implementations.
Namespace
Drupal\purge\Plugin\Purge\PurgerCode
public function getIdealConditionsLimit();