On Sat, Jan 27, 2001 at 09:32:56PM +0300, Artem Koutchine wrote:
Hmm.. So ID is not PRIMARY KEY (not UNIQUE index).. That makes it
harder. A lot harder. A lot depends now on how many records per ID
you have there on average. If you you have only, say, 50 ids then
you'll be slower.
Are you sure that your select is in fact using the index on that column? Could
you please explain select for us.
John Jensen wrote:
To: "Scott Gerhardt" [EMAIL PROTECTED]
From what I have heard from a local guru. you shoud double that
again. I had mysql working fine on 150 meg for
Have you tried adding an index on id?
-Original Message-
From: taree [mailto:taree]On Behalf Of Manuel Capinha
Sent: January 27, 2001 12:10 PM
To: [EMAIL PROTECTED]
Subject: 3 million+ records problems.
Hi!
I've got a table with 3 million+ records. This table has only to
Yes, that was the first thing i tried. The id column is indexed.
Scott Gerhardt wrote:
Have you tried adding an index on id?
-Original Message-
From: taree [mailto:taree]On Behalf Of Manuel Capinha
Sent: January 27, 2001 12:10 PM
To: [EMAIL PROTECTED]
Subject: 3 million+
From a mysqldump:
#
# Table structure for table 'names'
#
CREATE TABLE names (
id int(10) unsigned DEFAULT '0' NOT NULL,
name varchar(80) DEFAULT '' NOT NULL,
KEY id (id)
);
The machine is an Intel Celeron 533Mhz, with 64 mb of RAM, with dual 10
GB EIDE hard drives (doing RAID), running
Adding another 192megs of ram or so would really boost performance.
When I increased the RAM on my PIII 450Mhz from 128 to 256Mb, performance
almost doubled for most queries on a 72k record table.
From a mysqldump:
#
# Table structure for table 'names'
#
CREATE TABLE names (
