Maybe I don't understand how Boost populates, but I'm a little bit confused and hoping someone can clarify for me.

I do not run the Boost crawler, just caching as pages get touched. Today I found my boost_cache_relationships table was about 3G in size. I discovered this right after MySQL spazzed out on me.

I truncated the table, and within a minute or so, there 38,000+ rows in the table... and then nothing. This is odd to me because I only server about 21,000 pages per day.

Perhaps I don't understand how boost populates it's data, but I'm not sure why so many rows, or why they just suddenly stopped. Even worse, how did I end up with 3G worth of data in that table?

Any tips folks?

Comments

mikeytown2’s picture

mikeytown2 CreditAttribution: mikeytown2 commented

Sounds like your using a lot of blocks that where created by a view.
#785766: Only capture certain views in the relationship table is a hack I made if this is the case.

The boost relationship table creates 1 entry for each node that appears on that page. So if you have 5 view blocks each containing 10 nodes that's 50 entries in the relationship table. This is overkill and I realize that. Currently working on a solution. It's technically correct since if that node changes you would want all related pages containing that information to be expired and re-cached. It gets out of hand though so I need a way to control it.

djudd’s picture

djudd CreditAttribution: djudd commented

miketown2, you sir are impressive. No matter what problem I seem to have, you've already developed a solution.

Yes, I use a lot of views dependent blocks, my site (being a newspaper) revolves around lots of dynamic content. I've applied the patch, and I'll let you know how it works.

Thanks again sir!

mikeytown2’s picture

mikeytown2 CreditAttribution: mikeytown2 commented

If you wish to keep these blocks dynamic try this module out
http://drupal.org/project/ajaxify_regions
The 1.1 version is usable from my point of view (1.0 was junk IMHO).