Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
Sai5i Posted June 8, 2022 Posted June 8, 2022 (edited) Hello, I have database size of around 18.41GB, which is insane in my opinion as there are about 22.5k topics, 104k posts, and 10k members. This is the summary the hosting provider sent me today. DB: Size = 18.41 GB Table: ibf_core_cache , Size: 8.7211 GB Table: ibf_forums_posts , Size: 0.1651 GB Table: ibf_core_search_index , Size: 0.1566 GB Table: ibf_core_message_posts , Size: 0.0170 GB Table: ibf_core_attachments , Size: 0.0135 GB I have looked into admin and can't find an option to clear the core_cache table. But the problem is that even if we minus the whole core_cache table, the database is still over 9GB. That's huge as well. Another problem is that database size is increasing day by day but the tables which are taking most data are the same. Please take a look at the summary the hosting provider sent me on 1st June. DB: Size = 18.21 GB Table: ibf_core_cache , Size: 8.7211 GB Table: ibf_forums_posts , Size: 0.1651 GB Table: ibf_core_search_index , Size: 0.1566 GB Table: ibf_core_message_posts , Size: 0.0170 GB Table: ibf_core_attachments , Size: 0.0135 GB And it was 17.41GB around 20 days ago on May 18, 2022. DB: Size = 17.41 GB Table: ibf_core_cache , Size: 8.7211 GB Table: ibf_forums_posts , Size: 0.1651 GB Table: ibf_core_search_index , Size: 0.1566 GB Table: ibf_core_message_posts , Size: 0.0170 GB Table: ibf_core_attachments , Size: 0.0135 GB If you look at all the tables, the size is almost exactly the same. Yet 1GB of data increased for overall database size in just 20 days. This is strange. Can please someone tell me how to clear core_cache data? Is it okay to delete all entries in this table via the MySQL tool? Is there any option/cron in the admin section? Any idea, what else could be taking so much space? I would really appreciate help on this issue. Thanks Edited June 8, 2022 by Sai5i
Management Matt Posted June 8, 2022 Management Posted June 8, 2022 MySQL can hold onto a lot of data even when you delete rows. You can consider running a command like TRUNCATE ibf_core_cache via your SQL manager (always make sure you have a back-up, etc). It's safe enough to do this on core_cache as as the name suggests, it's just a place to store computed data for re-use. You'll probably find the usage of the core_cache table drops drastically.
Recommended Posts