INNODB INDEX SIZE

--001636e1fa2c4f345d046c9902ff
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi guys,

On MIS (management information system) server we have 16GB of physical
memory. 10GB has been allocated to innodb_buffer_pool_size. Database size is
around 500GB and some tables contains 600millions records.

my question is if innodb index_length(25GB) is greater than
data_length(20GB). How innodb manage and execute (select query) the join
between the bigger table which contains 500millions and 600millions records.
Although innodb_buffer_pool has been allocated only 10GB.

Any response is highly appreciated.
Thanks in advance.

Thanks,
Krishna

--001636e1fa2c4f345d046c9902ff--

Re: INNODB INDEX SIZE

--0016e6475fc66a2fc1046d3c9e4c
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi.
I think innodb will split these into many small pieces and then merge them
to execute.

On Thu, Jun 18, 2009 at 1:52 PM, Krishna Chandra Prajapati <
prajapatikc@gmail.com> wrote:

> Hi guys,
>
> On MIS (management information system) server we have 16GB of physical
> memory. 10GB has been allocated to innodb_buffer_pool_size. Database size
> is
> around 500GB and some tables contains 600millions records.
>
> my question is if innodb index_length(25GB) is greater than
> data_length(20GB). How innodb manage and execute (select query) the join
> between the bigger table which contains 500millions and 600millions
> records.
> Although innodb_buffer_pool has been allocated only 10GB.
>
> Any response is highly appreciated.
> Thanks in advance.
>
> Thanks,
> Krishna
>



--
David Yeung,
MySQL Senior Support Engineer,
Sun Gold Partner.
My Blog:http://yueliangdao0608.cublog.cn

--0016e6475fc66a2fc1046d3c9e4c--

Re: INNODB INDEX SIZE

--000e0cd1130aae7196046d4cb3cc
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Thanks, I am looking answer internally how the thinks work.

Regards,
Krishna

On Fri, Jun 26, 2009 at 2:33 PM, Moon's Father wrote:

> Hi.
> I think innodb will split these into many small pieces and then merge them
> to execute.
>
>
> On Thu, Jun 18, 2009 at 1:52 PM, Krishna Chandra Prajapati <
> prajapatikc@gmail.com> wrote:
>
>> Hi guys,
>>
>> On MIS (management information system) server we have 16GB of physical
>> memory. 10GB has been allocated to innodb_buffer_pool_size. Database size
>> is
>> around 500GB and some tables contains 600millions records.
>>
>> my question is if innodb index_length(25GB) is greater than
>> data_length(20GB). How innodb manage and execute (select query) the join
>> between the bigger table which contains 500millions and 600millions
>> records.
>> Although innodb_buffer_pool has been allocated only 10GB.
>>
>> Any response is highly appreciated.
>> Thanks in advance.
>>
>> Thanks,
>> Krishna
>>
>
>
>
> --
> David Yeung,
> MySQL Senior Support Engineer,
> Sun Gold Partner.
> My Blog:http://yueliangdao0608.cublog.cn
>

--000e0cd1130aae7196046d4cb3cc--