View the original community article here
Last tested: Jan 22, 2021
Since new rows are constantly being added to tables in the internal db, it’s no surprise that the tables can grow to be unmanageably large quite quickly. Since the the internal db tables are also constantly being queried, it benefits us to keep the tables at a manageable size in order to maintain optimal performance. That’s why we prune some tables accessible via system activity. Certain tables are pruned based on the number of rows in the table, while other tables are pruned based on the number of historical days that the data represents.