jair101 Posted May 9, 2020 Share Posted May 9, 2020 I just noticed that the table core_file_logs is pretty big, 500MB, taking about 20% of the entire db size. From the contents of the table I cannot identify what it is storing, but the "logs" in the name implies that it is probably something that can be pruned 🙂  What is stored here, is it safe to truncate and is there any way we can control its size from an ACP setting or something? Link to comment Share on other sites More sharing options...
Daniel F Posted May 9, 2020 Share Posted May 9, 2020 There’s a setting on the ACP file settings page to remove old data from the table. Please make sure that it’s active jair101 1 Link to comment Share on other sites More sharing options...
jair101 Posted May 9, 2020 Author Share Posted May 9, 2020 Found it and reduced it from 90 to 30 days. Hope it helps. Link to comment Share on other sites More sharing options...
Daniel F Posted May 9, 2020 Share Posted May 9, 2020 You could trigger the cleanup tasks several times manually and see if it helps . Link to comment Share on other sites More sharing options...
jair101 Posted May 9, 2020 Author Share Posted May 9, 2020 2 minutes ago, Daniel F said: You could trigger the cleanup tasks several times manually and see if it helps . The amount of rows dropped from 25k to 14k, but the size is more or less the same. Reduced it 1 day, 25 rows, still the same size, lol. Ran optimize on the table - everything is back in order, maybe I should have started with that 🙂 Link to comment Share on other sites More sharing options...
Recommended Posts