Change the following parameter:
myisam_sort_buffer_size=300MB
Larger than here.
myisam_max_sort_file_size=10GB
Reduce this value to 30% of your real memory.
On Tue, May 13, 2008 at 7:10 PM, Ananda Kumar <[EMAIL PROTECTED]> wrote:
> Hi Krishna,
> how do i make my index to get more key blocks
>
> O
Hi Krishna,
how do i make my index to get more key blocks
On 5/13/08, Krishna Chandra Prajapati <[EMAIL PROTECTED]> wrote:
>
> Hi anand,
>
> PRIMARY KEY (`id`),
> KEY `KI_IDX_0805090456` (`words`,`id`),
> KEY `CI_IDX_0805090456` (`lf_id`)
>
> Since id is a primary key. Then why again indexing o
Hi anand,
PRIMARY KEY (`id`),
KEY `KI_IDX_0805090456` (`words`,`id`),
KEY `CI_IDX_0805090456` (`lf_id`)
Since id is a primary key. Then why again indexing on id is being created
(`words`,`id`). It will be a duplicate index on id. words is a varchar
type. So instead of creating fulltext index
| Handler_commit| 25802690 |
| Handler_delete| 100 |
| Handler_discover | 0|
| Handler_prepare | 10370014 |
| Handler_read_first| 88920|
| Handler_read_key
At 08:18 AM 5/12/2008, you wrote:
Hi All,
We have a table which is around 100 Million rows. Its a myisam table, but
the db default is innodb.
CREATE TABLE `dc_data` (
`id` decimal(22,0) NOT NULL,
`words` varchar(255) NOT NULL,
`lf_id` decimal(22,0) NOT NULL,
`occurence` bigint(20) NOT NUL
myisam_max_sort_file_size=10GB
You have alloted 10GB memory to myisam_max_sort_file_size, The system has
8GB of memory.
send show global status;
On Mon, May 12, 2008 at 6:48 PM, Ananda Kumar <[EMAIL PROTECTED]> wrote:
> Hi All,
> We have a table which is around 100 Million rows. Its a myisam ta
