MySQL Performance: MySQL => Merge table Vs Big Table

Members

Help

Home

Home » Performance » MySQL » Merge table Vs Big Table

Show: Today's Messages :: Show Polls :: Message Navigator

Merge table Vs Big Table [message #2712]

Mon, 10 March 2008 04:47

yobogs
Messages: 1
Registered: March 2008

Junior Member

Hello,

First, sorry for my English Wink

I have a Merge table with 70 millions lines (in 70 tables) and i insert 1 million line each week.

I use this merge table to insert, select and delete data.

I would like to know if it's better for performance (insert and select, i don't make many delete) to have 1 table with 70 millions lines or my merge table.

Tks for your help

Report message to a moderator

Re: Merge table Vs Big Table [message #2728 is a reply to message #2712 ]

Fri, 14 March 2008 18:38

sterin
Messages: 324
Registered: March 2007
Location: Sweden

Senior Member

Are you always selecting/inserting using the merge table and not the child tables?

Have you split out the child tables on different disks or are they all stored on the same disk?

If your answers are yes to the two above you will probably not notice any direct difference between using merge or just one large table.
In that case the load on the server is mostly dependent on the total size of the database and then it doesn't really matter in what way the data i stored. The size is still the same and it is still as hard to search through.

Report message to a moderator

Previous Topic:	Optimizing ORDER BY - Returned data is not in the expected order
Next Topic:	HA with DRBD and/or Replication

Goto Forum:

-=] Back to Top [=-

[ Generate printable PDF ] [ Syndicate this forum (XML) ] [

]

Current Time: Fri Jul 10 00:59:52 EDT 2009

Total time taken to generate the page: 0.02894 seconds

.:: Contact :: Home ::.

MySQL is a trademark of Sun Microsystems.
InnoDB is a trademark of Oracle Corp.

Percona Performance Forums are a service of Percona, Inc.
Not affiliated with Sun Microsystems or Oracle Corp.