mysql issue

Jason Van Patten jason at infogenix.com
Wed Feb 8 15:44:19 MST 2012


On 2/8/2012 3:13 PM, Paul Seamons wrote:
> I'd second that, but I'd add a "be sure to add innodb_file_per_table=1
> to the my.cnf
Be very careful with that entry. It can wreck your seek times once you 
get really large data sets and can make load balancing moot.
Jason
>
> Paul
>
> On 02/08/2012 12:24 PM, Jason Van Patten wrote:
>> On 2/8/2012 11:50 AM, Merrill Oveson wrote:
>>> MyISAM
>>>
>>>
>> That might be the reason mysql locked in the first place. You get one
>> rouge query that takes too long and every other query hitting  that
>> table and all joins has to wait for it. InnoDB is a little slower, but
>> it ill only lock rows affected by the query instead of the whole
>> table/tables. Unless you are index text columns i would recommend
>> switching to Innodb or setting up a watchdog on your process list. Most
>> times the watchdog is a good move just so you have time to get innodb
>> running (select * statements will all need to get paired down to the
>> minimum)
>>
>> /*
>> PLUG: http://plug.org, #utah on irc.freenode.net
>> Unsubscribe: http://plug.org/mailman/options/plug
>> Don't fear the penguin.
>> */
>>
>
> /*
> PLUG: http://plug.org, #utah on irc.freenode.net
> Unsubscribe: http://plug.org/mailman/options/plug
> Don't fear the penguin.
> */
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.1913 / Virus Database: 2112/4796 - Release Date: 02/08/12
>
>



More information about the PLUG mailing list