# Large no of rows post\_timings table

**URL:** <https://meta.discourse.org/t/large-no-of-rows-post-timings-table/61718>\
**Category:** Support\
**Created:** [April 27, 2017, 1:11pm UTC](https://meta.discourse.org/t/large-no-of-rows-post-timings-table/61718 "2017-04-27T13:11:57Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![junaid\_pk14](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/junaid_pk14/32/67840_2.png) [@junaid\_pk14](https://meta.discourse.org/u/junaid_pk14)\
**Post date:** [April 27, 2017, 1:11pm UTC](https://meta.discourse.org/t/large-no-of-rows-post-timings-table/61718/1 "2017-04-27T13:11:57Z")

</div>

Hello Guys,

After running Discourse forum, records in the post\_timings table has grown to much. Now there are 13,373,115 rows in this table. Can we clear this table?

Regards,  
Junaid

---

<div class="post-metadata">

**Author:** ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)\
**Post date:** [April 27, 2017, 1:18pm UTC](https://meta.discourse.org/t/large-no-of-rows-post-timings-table/61718/2 "2017-04-27T13:18:03Z")

</div>

Why do you want to clear the `post_timings` table? Are you experiencing any performance issues?

---

<div class="post-metadata">

**Author:** ![junaid\_pk14](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/junaid_pk14/32/67840_2.png) [@junaid\_pk14](https://meta.discourse.org/u/junaid_pk14)\
**Post date:** [April 27, 2017, 1:21pm UTC](https://meta.discourse.org/t/large-no-of-rows-post-timings-table/61718/3 "2017-04-27T13:21:52Z")

</div>

I didn’t check yet the performance yet but i was expecting that large no of records will definitely hit the performance when other tables join this. What are your thoughts?

---

<div class="post-metadata">

**Author:** ![eviltrout](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviltrout/32/5275_2.png) [@eviltrout](https://meta.discourse.org/u/eviltrout)\
**Post date:** [April 27, 2017, 2:55pm UTC](https://meta.discourse.org/t/large-no-of-rows-post-timings-table/61718/4 "2017-04-27T14:55:08Z")

</div>

If you clear that table Discourse will lose track of what people have read. The table is indexed and you shouldn’t have any problems with the way Discourse accesses it. I just looked at one of the sites we host which has 93M records in there and it’s still going smoothly.

For the record, we _vastly_ prefer it when people come showing an example of how something is a problem. Theoretical issues can’t be fixed.

---

<div class="post-metadata">

**Author:** ![junaid\_pk14](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/junaid_pk14/32/67840_2.png) [@junaid\_pk14](https://meta.discourse.org/u/junaid_pk14)\
**Post date:** [April 28, 2017, 2:11pm UTC](https://meta.discourse.org/t/large-no-of-rows-post-timings-table/61718/5 "2017-04-28T14:11:08Z")

</div>

@eviltrout Thank you so much for detail reply. I agreed with your opinion about fixing the issue. Our records has increased to 13.4 millions.

Best Regards,  
Junaid

---

<div class="post-metadata">

**Author:** ![eviltrout](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviltrout/32/5275_2.png) [@eviltrout](https://meta.discourse.org/u/eviltrout)\
**Post date:** [April 28, 2017, 2:23pm UTC](https://meta.discourse.org/t/large-no-of-rows-post-timings-table/61718/6 "2017-04-28T14:23:21Z")

</div>