On 2012/05/24 07:37, Alex Schaft wrote:
> You are selecting a record based on the value of data_id and
> thold_enabled, but don't have an index on either? Add an index for both.
> If data_id is unique, then you would only need an index on that.
>
> Alex
>
On second thought, an index on thold_enabl
On 2012/05/24 04:10, Yu Watanabe wrote:
> 2. Instead INDEXes and schema design must be studied. Please provide:
> SHOW CREATE TABLE
> | thold_data | CREATE TABLE `thold_data` (
> `id` int(11) NOT NULL auto_increment,
> `rra_id` int(11) NOT NULL default '0',
> `data_id` int(11) NOT NU
Rick
Thank you for the reply.
>1. There are only a few things worth tuning -- see
>http://mysql.rjweb.org/doc.php/memory (they don't include the ones you tried)
>
The page is really cool. Its very simple and easy to understand.
>2. Instead INDEXes and schema design must be studied. Please p
100% CPU --> A slow query. Tuning will not help. Period.
1. There are only a few things worth tuning -- see
http://mysql.rjweb.org/doc.php/memory (they don't include the ones you tried)
2. Instead INDEXes and schema design must be studied. Please provide:
SHOW CREATE TABLE
SHOW TABLE SIZE
EXP
On 23 May 12, at 03:15, Walter Heck wrote:
> Also, have you looked at MariaDB 5.5?
I've been playing with it a bit. Their "virtual columns" enhancement is pretty
cool -- something I miss from my FileMaker days.
Economics is extremely useful as a form of employment for economist
Hi,
How much ever tuning you do at my.cnf will not help much, if you do not
tune your sql's.
Your first priority should be tune sql's, which will give you good
performance even with decent memory allocations and other settings
regards
anandkl
On Wed, May 23, 2012 at 3:45 PM, Andrew Moore wrote:
Yu,
The upgrade to 5.5 that Jonny advises should NOT your first action. If
MySQL is mis-configured on 5.0 it will likely be misconfigured on 5.1 and
5.5. Test your application thoroughly on the new version before heeding
that advice. Read the change logs and known bugs. Running the upgrade might
s
