2 RT instances pointing to a single database instance

Hi,

Lots of great stuff on this list and the wiki about multiple instances
pointing to different database instances (rt_math, rt_english). However,
I interested to know if anyone has set up multiple instances pointing to
the same db instance?

Why?

Out support office in the UK is seeing very slow response times, we’d
like to try hosting an instance in the UK, which connects to the same
database that the instance here in California uses. Hopefully, serving
the pages locally will improve page load speed.

My biggest concern is around database locking – does RT 3.2.1 do
database level locking or application level locking. Not worth
corrupting my database!

thanks,

Chris

Hi,

Lots of great stuff on this list and the wiki about multiple instances
pointing to different database instances (rt_math, rt_english). However,
I interested to know if anyone has set up multiple instances pointing to
the same db instance?

I have. I might have a production 3.4.2 instance, and a test 3.6.1 instance.
(Sometimes this is ok if the database schema is the same, otherwise not.)
Makes it easy to try out 3.6.1 in a real situation, without requiring
eveyone to upgrade at the same time.

Anyway, your scenario is exactly what I planned on, if I need
extra performance. I don’t think there would be a locking issue,
since you’d have the same issue between multiple fcgi processes
on the “same” RT instance.

  bobg

You can setup multiple RT instances pointing to the same db , just set
your database variables in the RT_SiteConfig …
Though I would suggest you consider the network implications, there are
lots and lots of queries (I worked it out to be 216 queries to display
the the home page (RT at a glance) with just 16 tickets displayed …all
these queries will be going over your transatlantic link …
Regards;
Roy

Chris Haag wrote: