# Large table

**URL:** <https://forums.percona.com/t/large-table/752>\
**Category:** Other MySQL® Questions\
**Created:** [May 8, 2008, 3:19am UTC](https://forums.percona.com/t/large-table/752 "2008-05-08T03:19:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mrl22](https://avatars.discourse-cdn.com/v4/letter/m/d07c76/32.png) [@mrl22](https://forums.percona.com/u/mrl22)\
**Post date:** [May 8, 2008, 3:19am UTC](https://forums.percona.com/t/large-table/752/1 "2008-05-08T03:19:15Z")

</div>

Hi,

I have a script that creates between 60 and 2000 records a minute in a table with only 4 columns, over time this table will get very large…

Is there any way I can build the database for this to run fast even with large ammounts of data?

Richrad

---

<div class="post-metadata">

**Author:** ![mwallace](https://avatars.discourse-cdn.com/v4/letter/m/ee59a6/32.png) [@mwallace](https://forums.percona.com/u/mwallace)\
**Post date:** [May 9, 2008, 1:11am UTC](https://forums.percona.com/t/large-table/752/2 "2008-05-09T01:11:03Z")

</div>

Partitioning and indexes. What’s the read load expected to be vs. the write load?

---

<div class="post-metadata">

**Author:** ![mrl22](https://avatars.discourse-cdn.com/v4/letter/m/d07c76/32.png) [@mrl22](https://forums.percona.com/u/mrl22)\
**Post date:** [May 9, 2008, 6:32am UTC](https://forums.percona.com/t/large-table/752/3 "2008-05-09T06:32:14Z")

</div>

I can imagine the read to be alot more…

As there will be only one script that will write a load of data once every minute… but multiple clients will generate graphs and stats from that data throughout the day…