We have been running rt 1.0 for a very long time. We
have finally decided to make the switch to 2.0. The
problem is, we have approx 65,000 records. When we
run the import-1.0-to-2.0 script, everything seems
fine for awhile… until about 12,00 records or so. It
starts getting really slow… then really really slow…
at about 22,000 or so, its at a snails pace… 5 days
later we were at 31,000. This is the ONLY thing
running on a p4 1.4 scsi FreeBSD system with 512 meg
ram. I even tried this on a production server with
768 meg ram (Solaris platform) and had the same
problem. I don’t think I can wait weeks for this to
convert our database. Is there any solution? I have
searched the archives for this list and I have not
seen any answers.
We are using mySQL in case you missed that in the
subject line.
Thank you!
Scott
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
We have been running rt 1.0 for a very long time. We
have finally decided to make the switch to 2.0. The
problem is, we have approx 65,000 records. When we
run the import-1.0-to-2.0 script, everything seems
fine for awhile… until about 12,00 records or so. It
starts getting really slow… then really really slow…
at about 22,000 or so, its at a snails pace… 5 days
later we were at 31,000. This is the ONLY thing
running on a p4 1.4 scsi FreeBSD system with 512 meg
ram.
Two suggestions:
Find out where it is blocking – is it disk I/O, memory, network (may
not be involved) or just MySQL? If, e.g., ‘top’ shows low CPU util. and
free memory, and the network’s not involved, try #2…
MySQL seems to me to be a likely culprit. The default configuration
was never meant to be beat upon with a 64K record import – search the
archives for high-load MySQL configuration, or use good old Google.
On Tue Sep 09/03/02, 2002 at 05:45:36PM -0700, Scott wrote:
Hello,
We have been running rt 1.0 for a very long time.
We
have finally decided to make the switch to 2.0.
The
problem is, we have approx 65,000 records. When
we
run the import-1.0-to-2.0 script, everything seems
fine for awhile… until about 12,00 records or so.
It
starts getting really slow… then really really
slow…
at about 22,000 or so, its at a snails pace… 5
days
later we were at 31,000. This is the ONLY thing
running on a p4 1.4 scsi FreeBSD system with 512
meg
ram.
Two suggestions:
Find out where it is blocking – is it disk I/O,
memory, network (may
not be involved) or just MySQL? If, e.g., ‘top’
shows low CPU util. and
free memory, and the network’s not involved, try #2…
MySQL seems to me to be a likely culprit. The
default configuration
was never meant to be beat upon with a 64K record
import – search the
archives for high-load MySQL configuration, or use
good old Google.
Top shows that perl is using 97.6% CPU. Nothing else
is even close. Any ideas?
Try throwing some debugging statements into the MigrateTickets
function to see which code is running slowly. Repeat as needed
for such things as MigrateTransactions.
Phil Homewood, Systems Janitor, www.SnapGear.com pdh@snapgear.com Ph: +61 7 3435 2810 Fx: +61 7 3891 3630
SnapGear - Custom Embedded Solutions and Security Appliances
Thanks for the suggestion. The problem is that I am
not a perl techie. We just need to import some
records ;-). Has anyone else upgraded 1.0 to 2.0 with
60,000 or so records? I think the upgrade script is
definetly the problem, but I don’t know how to write a
new one. Are there any other upgrade scripts?
Top shows that perl is using 97.6% CPU. Nothing
else
is even close. Any ideas?
Try throwing some debugging statements into the
MigrateTickets
function to see which code is running slowly. Repeat
as needed
for such things as MigrateTransactions.
Phil Homewood, Systems Janitor, www.SnapGear.com pdh@snapgear.com Ph: +61 7 3435 2810 Fx: +61 7 3891
3630
SnapGear - Custom Embedded Solutions and Security
Appliances
I migrated ours from 1.0 to 2.0.13 and I had about 65,000 tickets
It worked fine with the upgrade script----- Original Message -----
From: “Scott” pdxguy31@yahoo.com
To: rt-users@lists.fsck.com
Sent: Friday, September 06, 2002 1:56 AM
Subject: Re: [rt-users] converting rt 1.0 mysql database SLOW
Hi Phil,
Thanks for the suggestion. The problem is that I am
not a perl techie. We just need to import some
records ;-). Has anyone else upgraded 1.0 to 2.0 with
60,000 or so records? I think the upgrade script is
definetly the problem, but I don’t know how to write a
new one. Are there any other upgrade scripts?
Top shows that perl is using 97.6% CPU. Nothing
else
is even close. Any ideas?
Try throwing some debugging statements into the
MigrateTickets
function to see which code is running slowly. Repeat
as needed
for such things as MigrateTransactions.
Phil Homewood, Systems Janitor, www.SnapGear.com pdh@snapgear.com Ph: +61 7 3435 2810 Fx: +61 7 3891
3630
SnapGear - Custom Embedded Solutions and Security
Appliances
I migrated ours from 1.0 to 2.0.13 and I had about
65,000 tickets
It worked fine with the upgrade script
----- Original Message -----
From: “Scott” pdxguy31@yahoo.com
To: rt-users@lists.fsck.com
Sent: Friday, September 06, 2002 1:56 AM
Subject: Re: [rt-users] converting rt 1.0 mysql
database SLOW
Hi Phil,
Thanks for the suggestion. The problem is that I
am
not a perl techie. We just need to import some
records ;-). Has anyone else upgraded 1.0 to 2.0
with
60,000 or so records? I think the upgrade script
is
definetly the problem, but I don’t know how to
write a
new one. Are there any other upgrade scripts?
Top shows that perl is using 97.6% CPU.
Nothing
else
is even close. Any ideas?
Try throwing some debugging statements into the
MigrateTickets
function to see which code is running slowly.
Repeat
as needed
for such things as MigrateTransactions.
Phil Homewood, Systems Janitor, www.SnapGear.com pdh@snapgear.com Ph: +61 7 3435 2810 Fx: +61 7
3891
3630
SnapGear - Custom Embedded Solutions and
Security
Appliances