Further import woes

Well, I seem to have a successful import going, for adequately broad
definitions of “success.”

Having copied the mysql RT1 database to the same machine that is to
house the RT2 setup seems to have solved the mysterious connection
death problems. Unfortunately, the import is zipping along at about
43 minutes per 1,000 tickets. This will make our database of some
28,000 tickets take about 24 hours. Not so bad in itself, since of
course it only needs to be done once, but I’d rather avoid that long a
service outage, since it would be good to avoid needing to re-import
again after the main import is done to get the delta in.

Any suggestions? Is this wholly bizarre, indicating some mysql
misconfiguration? It seems peculiar given how quickly a web page
comes up in RT, which must use a similar query, but presumably the
logic to transform the mysql records into a Pg insert is
time-consuming–I don’t know. It’s running on a pIII-550, fwiw.

Any clues gratefully accepted.

–JB

I don’t think its really an issue with your setup, I did a limited
import of about 200 tickets and this took approx 10 minutes…
of cause this means our database of 220000+ tickets is going to take
awhile to process :)On Wed, Sep 26, 2001 at 04:54:28PM -0700, J B Bell wrote:

Well, I seem to have a successful import going, for adequately broad
definitions of “success.”

Having copied the mysql RT1 database to the same machine that is to
house the RT2 setup seems to have solved the mysterious connection
death problems. Unfortunately, the import is zipping along at about
43 minutes per 1,000 tickets. This will make our database of some
28,000 tickets take about 24 hours. Not so bad in itself, since of
course it only needs to be done once, but I’d rather avoid that long a
service outage, since it would be good to avoid needing to re-import
again after the main import is done to get the delta in.

Any suggestions? Is this wholly bizarre, indicating some mysql
misconfiguration? It seems peculiar given how quickly a web page
comes up in RT, which must use a similar query, but presumably the
logic to transform the mysql records into a Pg insert is
time-consuming–I don’t know. It’s running on a pIII-550, fwiw.

Any clues gratefully accepted.

–JB


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Matthew Watson
Development , Netspace Online Systems
mwatson@netspace.net.au