Home/ Questions/Q 111889
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T02:27:30+00:00

I’m writing an app with a MySQL table that indexes 3 columns. I’m concerned

  • 0

I’m writing an app with a MySQL table that indexes 3 columns. I’m concerned that after the table reaches a significant amount of records, the time to save a new record will be slow. Please inform how best to approach the indexing of columns.

UPDATE

I am indexing a point_value, the user_id, and an event_id, all required for client-facing purposes. For an instance such as scoring baseball runs by player id and game id. What would be the cost of inserting about 200 new records a day, after the table holds records for two seasons, say 72,000 runs, and after 5 seasons, maybe a quarter million records? Only for illustration, but I’m expecting to insert between 25 and 200 records a day.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Index what seems the most logical (that should hopefully be obvious, for example, a customer ID column in the CUSTOMERS table).

    Then run your application and collect statistics periodically to see how the database is performing. RUNSTATS on DB2 is one example, I would hope MySQL has a similar tool.

    When you find some oft-run queries doing full table scans (or taking too long for other reasons), then, and only then, should you add more indexes. It does little good to optimise a once-a-month-run-at-midnight query so it can finish at 12:05 instead of 12:07. However, it’s a huge improvement to reduce a customer-facing query from 5 seconds down to 2 seconds (that’s still too slow, customer-facing queries should be sub-second if possible).

    More indexes tend to slow down inserts and speed up queries. So it’s always a balancing act. That’s why you only add indexes in specific response to a problem. Anything else is premature optimization and should be avoided.

    In addition, revisit the indexes you already have periodically to see if they’re still needed. It may be that the queries that caused you to add those indexes are no longer run often enough to warrant it.

    To be honest, I don’t believe indexing three columns on a table will cause you to suffer unless you plan on storing really huge numbers of rows 🙂 – indexing is pretty efficient.

    After your edit which states:

    I am indexing a point_value, the user_id, and an event_id, all required for client-facing purposes. For an instance such as scoring baseball runs by player id and game id. What would be the cost of inserting about 200 new records a day, after the table holds records for two seasons, say 72,000 runs, and after 5 seasons, maybe a quarter million records? Only for illustration, but I’m expecting to insert between 25 and 200 records a day.

    My response is that 200 records a day is an extremely small value for a database, you definitely won’t have anything to worry about with those three indexes.

    Just this week, I imported a days worth of transactions into one of our database tables at work and it contained 2.1 million records (we get at least one transaction per second across the entire day from 25 separate machines). And it has four separate composite keys which is somewhat more intensive than your three individual keys.

    Now granted, that’s on a DB2 database but I can’t imagine IBM are so much better than the MySQL people that MySQL can only handle less than 0.01% of the DB2 load.

    • 0