My experience (atleast with the 3.23 series) is that full text indexing is
not worth the hassle if you have an existing HUGE database... I let mysql
run for about a day or two on a 20gb database (dont remember exactly how
many rows it had) before giving up (note this was using 3.23.39). I found on
such a large dataset the full text indexing didnt do very well (queries took
15-20 seconds on a pIII 700mghz 512megs of ram dedicated to mysql).

Anyhow... good luck, hope things turn out better for you than they did for
me.

ryan


----- Original Message -----
From: "Steve Rapaport" <[EMAIL PROTECTED]>
To: "MySQL List" <[EMAIL PROTECTED]>
Sent: Sunday, January 20, 2002 5:25 PM
Subject: Fulltext build 2 days and counting...


> Okay, does anyone know how long this will take?
> 22 million records, fulltext index on a single field, first 40 chars.
> record length 768 chars, variable.
>
> It's been running for 2 days, processlist quotes time at around 100000.
> Index file still growing occasionally, up to 3Gb.
>
> Should I let it continue or give up?  Will this take another 2 days?
> another week?  Anyone else with experience to get a rule of thumb?
>
> I'm using mysql  3.23.37 on a dual processor intel Redhat, 700Mhz, 1G ram.
>
> --
> Steve Rapaport
> still at large
>
>
> ---------------------------------------------------------------------
> Before posting, please check:
>    http://www.mysql.com/manual.php   (the manual)
>    http://lists.mysql.com/           (the list archive)
>
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail <[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>


---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to