[rt-users] RT Performance, Hardware

[Jesse Vincent]

Enhancements to the ACL system coming in the next major release should
significantly improve this. Soon, we'll have API calls for all the primitives
an ACL system should have.

	J


On Mon, Jun 24, 2002 at 04:23:56PM +0200, Bruce Campbell wrote:
> On Mon, 24 Jun 2002, Timo Hummel wrote:
> > The performance of RT also strongly depends on how many queues and
> > tickets are in the system. We run an RT system with >50 queues, and the
> > Quicksearch element (which shows the amount of new/open and resolved
> > tickets) takes almost 4 seconds, while as other elements go trough
> > pretty quick.
> 
> Hrm.  This is a wee bit on the bad side.  This could be fixed by caching
> the number of queues per ticket status every [regular time interval], and
> having simple Scrip-base {in,de}crements on any status change.
> 
> You lose absolute reliability of this output when lots of updates occur
> inside [regular time interval], but gain 4 seconds per load of the home
> page, which if you've got 50 queues visible to most people, is a lot.
> 
> Regards,
> 
> -- 
>                              Bruce Campbell                            RIPE
>                    Systems/Network Engineer                             NCC
>                  www.ripe.net - PGP562C8B1B                      Operations
> 
> 
> _______________________________________________
> rt-users mailing list
> rt-users at lists.fsck.com
> http://lists.fsck.com/mailman/listinfo/rt-users
> 
> Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm
> 

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