When running "drush cron" then there is no limit on how many saved searches will be checked. This is very bad when you migrate hundreds of thousands of job alerts that all want to be checked at the same time.
Symptoms:
* error message: Attempting to run cron while it is already running
* Gigabytes of RAM usage by the PHP process on the server
* Cron never finishes because search_api_saved_searches_cron() tries to process 70k saved searches.
Migrate thousands of saved searches that want to be checked and try to run cron.
Always apply the cron_batch_size limit, even when running through the PHP CLI. This ensures cron runs are predictable and don't exhaust server resources.
Active
1.0
Code
Not sure why the default batch limit is set to 10, that is way too low.
In Drupal 7 we use 500 for the variable search_api_saved_searches_load_max.
Should we update the default value on install to 500?