Announcement Module
No announcement yet.

single database vs multiple databases

Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • single database vs multiple databases

    I have an application that currently uses a single database with thousands of tables (MyISAM) containing hit counter data. Is there a performance benefit or loss in using multiple databases vs a single database? The current database is about 106GB on disk.

  • #2
    single vs. multiple databases on a machine? Not realy. But you should think about using "multiple" Tables or Partitioning )


    • #3
      The data is currently being kept in a table for each day (which is why there are 1000s of tables going back to every day since 2002) but if there is a more efficient storage mechanism recommended I am all ears. IT currently takes about 10 hours to do a restore of this backup (backup using mysqldump to file) and if we can lower our backup/restore times it would be all the better.


      • #4
        If you dont want your application go for partition.
        I would recommend to split it up into different tables. Speeds up dump and restore.

        You could also use merging tables and compress older data.


        • #5
          How does partition work? I don't think i have compressed tables either... Where is good documentation on how this is done and what the ramifications are?


          • #6
            Partitioning comes with 5.1 (


            • #7
              I recommend to use LVM snapshots for backups. MySQL data directory should be on LVM partition for it.