Re: indexing = NP complete??

2001-06-19 Thread Robin Senior
On Fri, 15 Jun 2001, Jeremy Zawodny wrote: > On Fri, Jun 15, 2001 at 12:53:04PM -0600, Chris Bolt wrote: > > > Is this machine basically dedicated to MySQL? If so, I'd try bumping > > > up the record_buffer to 16 or 32MB and see what that does. I've got it > > > set at 32MB on a server with 1GB o

Re: indexing = NP complete??

2001-06-15 Thread Jeremy Zawodny
On Fri, Jun 15, 2001 at 12:53:04PM -0600, Chris Bolt wrote: > > Is this machine basically dedicated to MySQL? If so, I'd try bumping > > up the record_buffer to 16 or 32MB and see what that does. I've got it > > set at 32MB on a server with 1GB of RAM. > > I'm looking at my-huge.cnf included with

RE: indexing = NP complete??

2001-06-15 Thread Chris Bolt
> Is this machine basically dedicated to MySQL? If so, I'd try bumping > up the record_buffer to 16 or 32MB and see what that does. I've got it > set at 32MB on a server with 1GB of RAM. I'm looking at my-huge.cnf included with mysql 3.23.39 and it has a record_buffer of 1M. Are the example confi

Re: indexing = NP complete??

2001-06-14 Thread Jeremy Zawodny
On Thu, Jun 14, 2001 at 12:43:41PM -0400, Robin Senior wrote: > On Thu, 14 Jun 2001, Jeremy Zawodny wrote: > > I have a few comments and questions: > > > > (1) Is this a unique index? If not, consider doing a partial index > > on the column. Index the first 32 characters or so. I'll save

Re: indexing = NP complete??

2001-06-14 Thread Robin Senior
On Thu, 14 Jun 2001, Jeremy Zawodny wrote: > I have a few comments and questions: > > (1) Is this a unique index? If not, consider doing a partial index > on the column. Index the first 32 characters or so. I'll save a > lot of disk I/O, memory, and CPU time but still yeild pretty

Re: indexing = NP complete??

2001-06-14 Thread Jeremy Zawodny
On Thu, Jun 14, 2001 at 11:31:32AM -0400, Robin Senior wrote: > > Just kidding! But it seems that way... > > Indexing a 7 million row VARCHAR(255) table took ~12 minutes on my Athlon > 1.33Ghz w/512MB. > Indexing a 77 million row VARCHAR(255) table has taken 9 DAYS, and still > hasn't finished. >

indexing = NP complete??

2001-06-14 Thread Robin Senior
Just kidding! But it seems that way... Indexing a 7 million row VARCHAR(255) table took ~12 minutes on my Athlon 1.33Ghz w/512MB. Indexing a 77 million row VARCHAR(255) table has taken 9 DAYS, and still hasn't finished. Obviously this isn't a linearly scaling operation, but it is seeming dang ne