endorse content contained within
this transmission.
> Date: Wed, 15 Oct 2008 17:09:42 +0530
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: Trouble with large data in MySql
> CC: mysql@lists.mysql.com
>
> Hi,
>
> 1. Since requestid is a primary key then wh
my query? What should I configure in mysql? Can you
> help me with this?
>
>
>
> I have 6GB RAM, 2 cores and 7200 RPM disk with 1TB size.
>
>
>
> Thanks in advance
>
> Karthik
>
>
>
>
>
> *From:* Krishna Chandra Prajapati [mailto:[EMAIL PROTECTE
ance
Karthik
From: Krishna Chandra Prajapati [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 15, 2008 3:43 PM
To: Karthik Pattabhiraman
Cc: mysql@lists.mysql.com
Subject: Re: Trouble with large data in MySql
Hi,
It depends on your query using join and sort. Also, on how much ram you
ha
attabhiraman
> *Cc:* mysql@lists.mysql.com
> *Subject:* Re: Trouble with large data in MySql
>
>
>
> Hi Karthik,
>
> You have many columns in a single table (although you can). But, if you
> break the below table into two tables ( Vertical partitioning). It will help
&
: Re: Trouble with large data in MySql
Hi Karthik,
You have many columns in a single table (although you can). But, if you
break the below table into two tables ( Vertical partitioning). It will
help you to run your query faster. You haven't shown join_buffer_size
and sort_buffer_size.
Sec
can u please show us the output of
show index from ;
On 10/14/08, Krishna Chandra Prajapati <[EMAIL PROTECTED]> wrote:
>
> Hi Karthik,
>
> You have many columns in a single table (although you can). But, if you
> break the below table into two tables ( Vertical partitioning). It will
> help
> yo
Hi Karthik,
You have many columns in a single table (although you can). But, if you
break the below table into two tables ( Vertical partitioning). It will help
you to run your query faster. You haven't shown join_buffer_size and
sort_buffer_size.
Secondly, check your all the queries with explain
Karthik,
I have included some of the parts of your original posting.
You may need to do some experiments, but these actions may help you
greatly. You may also want to consider the book "High Performance
MySQL", it has helped us a lot:
1. Make sure you have indexes on any column
Maybe you can paste back the results from an 'explain' statement...also
would be helpful to see the indexes on this table. Show create table
smas \G;
-Original Message-
From: Karthik Pattabhiraman [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 08, 2008 3:30 AM
To: mysql@lists.mysq
