Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.On one larger project have been using dev version of search_api_solr (checkout at this commit specifically ).
Decided to switch to a stable release and make an upgrade to 8.x-2.3.
Index info:
* Using direct indexing (when entity are created, immediately are tracked and indexed - on web request)
* 4 indexes (smallest 100k, largest 6+ million entries)
With dev version and small tweaks real-time indexing had performed OK (no performance drawbacks, even with biggest indexe)
With version 2.3 and the introduction of search_api_solr_search_api_items_indexed
* Each call off "search_api_solr_search_api_items_indexed" create query between 1-2 seconds.
* With that MySQL query times doubled on average as NewRelic data suggest (it's high traffic site, so this is significant usage increase)
Temporary fix: disable immediate Index - using only cron indexing.
But seems rather large performance drawback - https://www.drupal.org/node/3009282
I will definitely take a closer look tomorrow on search_api_solr_search_api_items_indexed (a little bit late here :-D).
It's possible to make a different approach there? what exactly is fixed with the introduction of this hook, haven't got a full grasp of the problem from the linked issue?
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 3021067.patch | 2 KB | mkalkbrenner |
Comments
Comment #2
mkalkbrennerThanks for pointing this out. We should add a config option to disable the feature (if you don't use streaming expressions) or to set a hardcoded limit or to do it at query time if required or to do it as cron task.
Comment #3
mkalkbrennerComment #5
mkalkbrennerComment #6
mkalkbrenner