Skip navigation links

MySQL Forums :: Performance :: HELP! making choises on Performance - Storage engine - Caching


Advanced Search

Re: HELP! making choises on Performance - Storage engine - Caching
Posted by: Rick James ()
Date: November 09, 2009 04:25PM

Several queries per second - yawn. Several per millisecond - that would be a challenge. So, probably don't need any caching.

MyISAM vs InnoDB -- You possibly want the security of InnoDB. If the master crashes, it can recover virtually everything, and do it more automatically than MyISAM. Changing a table to InnoDB:
ALTER TABLE foo ENGINE=InnoDB;
It will take time proportional to the size: hours if the table is gigabytes.

Any tables that don't have a PRIMARY KEY -- you should add one as you do the alter:
[/code]
ALTER TABLE foo
ADD COLUMN id INT UNSIGNED AUTO_INCREMENT NOT NULL,
PRIMARY KEY (id),
ENGINE=InnoDB;
[/code]
(Do them all in one step.)
If you already have a PRIMARY KEY, you don't need to change it.

User identifiable info being stored? Credit cards being stored? These are security issues that you should either avoid or solve before opening the doors.

Number of databases, number of tables -- do what is 'right' for the data.

Options: ReplyQuote


Subject Views Written By Posted
HELP! making choises on Performance - Storage engine - Caching 213 saif bechan 11/08/2009 08:31AM
Re: HELP! making choises on Performance - Storage engine - Caching 134 Rick James 11/09/2009 04:25PM
Re: HELP! making choises on Performance - Storage engine - Caching 122 saif bechan 11/10/2009 03:38AM
Re: HELP! making choises on Performance - Storage engine - Caching 142 Rick James 11/10/2009 09:29AM


Sorry, only registered users may post in this forum.