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.
It would be nice to enable the Admin to pause the crawler temporarily during heavy traffic or high CPU/RAM usage and the ability to resume crawling when required.
Thanks!
Comment | File | Size | Author |
---|---|---|---|
#5 | boost-613926.1.patch | 9.17 KB | mikeytown2 |
#4 | boost-613926.patch | 8.97 KB | mikeytown2 |
Comments
Comment #1
mikeytown2 CreditAttribution: mikeytown2 commentedAdded it to the roadmap.
Comment #2
Froggie-2 CreditAttribution: Froggie-2 commentedThanks!
Comment #3
mikeytown2 CreditAttribution: mikeytown2 commentedI think the better option is have the url_alias grab be smarter. Check against the database to see if that entry exists in the boost cache table. If it's not in the table then add it to the url crawler. This would make that setting be smarter and would make the stop crawler setting not as destructive on large runs of the url_alias. Doing a bulk insert for the sql should make it run faster as well.
Comment #4
mikeytown2 CreditAttribution: mikeytown2 commentedWorks how it should, just not how I envisioned the first time. This way is a lot faster then before. I need to check the finer points of the SQL before this gets committed.
Comment #5
mikeytown2 CreditAttribution: mikeytown2 commentedthis patch actually works
Comment #6
mikeytown2 CreditAttribution: mikeytown2 commentedcommitted
Comment #7
Froggie-2 CreditAttribution: Froggie-2 commented@Mikeytown: Thanks!