Home/ Questions/Q 55763
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T17:25:42+00:00

I once had a MySQL database table containing 25 million records, which made even

  • 0

I once had a MySQL database table containing 25 million records, which made even a simple COUNT(*) query takes minute to execute. I ended up making partitions, separating them into a couple tables. What i’m asking is, is there any pattern or design techniques to handle this kind of problem (huge number of records)? Is MSSQL or Oracle better in handling lots of records?

P.S the COUNT(*) problem stated above is just an example case, in reality the app does crud functionality and some aggregate query (for reporting), but nothing really complicated. It’s just that it takes quite a while (minutes) to execute some these queries because of the table volume

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. See Why MySQL could be slow with large tables and COUNT(*) vs COUNT(col)

    Make sure you have an index on the column you’re counting. If your server has plenty of RAM, consider increasing MySQL’s buffer size. Make sure your disks are configured correctly — DMA enabled, not sharing a drive or cable with the swap partition, etc.

    • 0