[rt-users] rt2-to-rt3 question

[Jesse Vincent]

On Wed, Apr 02, 2003 at 07:04:34AM +0200, Scott A. McIntyre wrote:
 
> Total import time was about 28 hours -- and this was on a test database, 
> non-live system and about 20000 less tickets than we have on our production 
> system.  We won't be migrating to rt3 anytime soon as a result, need to see 
> if the process can be sped up at all...

There's a reason the importer has an "incremental mode" that lets you do
a full import from rt2 to rt3 without turning off your rt2 system and
then doing an "incremental import" of only users and tickets that have
changed since the date you specify.  In the case of a high volume
system, I could see the need for an incremental import or _maybe_ even a
second incremental import for huge systems, but there's no reason you
should need to much actual downtime for a migration.


> unfortunately, for us, rt3 is 
> significantly slower than rt2 at the point that my users notice most: 
> initial login and presentation of their "home" page summary of 
> tickets....indeed, it is so slow that Safari times out (sixty seconds) and 
> generates an error.

I presume you _have_ tuned your MySQL 4 instance to use an apropriate
amount of RAM for your database size but that you've not had local staff 
do any profiling to see just _what_ is bogging down there. Feedback
there would be rather useful.


	Best,
	Jesse


-- 
http://www.bestpractical.com/rt  -- Trouble Ticketing. Free.