Prestashop: The table ps_layered_filter_block is growing fast

[weddingtextile]

Describe the bug
The table ps_layered_filter_block is growing fast (100-200 megabytes per day).
I have to clean the table every day.
This happened after updating PrestaShop from 1.7.4.3 to 1.7.6.2.

Additional information
PrestaShop version: 1.7.6.2
PHP version: 5.6.38
MySQL version: 5.7.13-6-log
Faceted search version: 3.4.1

[khouloudbelguith]

Hi @weddingtextile,

We need to retrieve the PHP error log and the debug mode report in order to find out what's wrong.
Don't you know how to get this information? Please read the following article:
http://build.prestashop.com/howtos/misc/how-to-create-bug-report/

Thanks!

[weddingtextile]

Very strange behavior. Within a week, the table increases to 100M, then decreases in size to 10M.
Before that, every few days I manually deleted the table when it increased to 150-200M.
I’m still watching.

[khouloudbelguith]

@weddingtextile, so the issue is not reproduced again?

Thanks!

[weddingtextile]

The table was growing to 100M from 10.02 to 22.02 and now 23.02. it size is 10M.
Is this a standard algorithm?
What condition does a table cleanup?

[khouloudbelguith]

Ping @PierreRambaud what do you think?

Thanks!

[PierreRambaud]

The more products and categories you have, the more combinaison are saved in the database, this is why this table is growing. Don't hesitate to add the clear-cache script in a cron :wink:

[weddingtextile]

Why was the table growing 10-12 days, and then, without external actions, it decreased?
Is this a standard algorithm?
What condition does a table cleanup?

[weddingtextile]

The problem has happened after updating PrestaShop from 1.7.4.3 to 1.7.6.2.

[PierreRambaud]

This table is truncated when you change an attribute, attribute group, category, feature, product, etc.
Or by running the ps_facetedsearch-clear-cache.php script, and using the "Clear cache" button.
it's not related to the PrestaShop version, the module is independent

[weddingtextile]

Thanks for the answer!
Something has changed in the algorithm Faceted search after the update. There were no problems with the table before.

[PierreRambaud]

@weddingtextile What version do you used before the update? There were no cache in the 2.*, and nothing change since the first 3.0.0.
It's not a problem to have a huge amount of data in a cache table, this is why this table exists :)

[weddingtextile]

Faceted Search version was 2.2.0
Ok, I'll close the issue.
Thanks All for help!

[gaelson]

Please tell me what's the real solution? My database grow 1Gb per day. please help

[weddingtextile]

The more products and categories you have, the more combinaison are saved in the database, this is why this table is growing. Don't hesitate to add the clear-cache script in a cron 😉

Use this solution

[gaelson]

Please could you show me how to set the clear-cache script?

[weddingtextile]

Copy URL on "Clear Cache" button.
Add it to cron jobs on hosting.

[gaelson]

Hello, Thank you for all.
Please when I click on Clear cache I get en error "Indexation failed".
Please how to ?

Le mer. 25 mars 2020 à 22:40, Ivan [e-mail] a écrit :

[image: ClearCache]
https://user-images.githubusercontent.com/44600313/77591887-a907e380-6ef9-11ea-82cb-3e96ad76de67.png
Copy URL on "Clear Cache" button.
Add it to cron jobs on hosting.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/PrestaShop/PrestaShop/issues/17318#issuecomment-604124507,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACT34U5MKFIVM7KRKT3J4J3RJKB4BANCNFSM4KKUKVXA
.

--
Gaël ADELA

"La logique vous conduira d'un point A à un point B. L'imagination et
l'audace vous conduiront où vous le désirez." *
*Albert Einstein

[weddingtextile]

Add a new issue

[zenerry]

Hi, I might be wrong, but I've 7 or 8 prestashop eCommerce running for my clients and I had the same issue only with the one I tryed to use Prestashop's CRON module, to run cron tasks for facets module (sitemap and product's gave me an error, as far as I can remember).
I disabled this facets CRON module and it seems not to be growing in such an exponential way. In my case it was about 1 or 2Gb per day with only 700 products.

[masiorama]

I experienced the same issue on PS 1.7.6.7 during the last week.
In 2-3 days without forcing the clear cache the table reached 700MB, and the overall DB reached 1GB.
Since my hosting limits the db dimension to 750MB it is a problem.
I just set a cron on my hosting to execute the clear cache once per day, during the night.
Still waiting to see what's the catch.