[rt-users] RT Performance, Hardware

[Manfred Hui]

----- Original Message -----
From: "Nate Amsden" <subscriptions at graphon.com>
To: <rt-users at lists.fsck.com>
Sent: Wednesday, June 26, 2002 5:12 AM
Subject: Re: [rt-users] RT Performance, Hardware


> Manfred Hui wrote:
> >
> > It should only take a few seconds to load a ticket, (we have around
30000
> > tickets, mysql, P3 600, 512 mb ram)
> >
> > Check that you have indexed the tables correctly, especially Tickets,
> > Transactions and Attachments.
>
> does this apply to only postgres ? i have a system running mysql and with
1000
> tickets its dog slow, some tickets take over a minute to load. p3-600 1gb
ram.

No, We use mysql as well.

To find out, connect to mysql and run this command:

mysql> show index from Transactions;
+--------------+------------+---------------+--------------+----------------
-+-----------+-------------+----------+--------+---------+
| Table        | Non_unique | Key_name      | Seq_in_index | Column_name
| Collation | Cardinality | Sub_part | Packed | Comment |
+--------------+------------+---------------+--------------+----------------
-+-----------+-------------+----------+--------+---------+
| Transactions |          0 | PRIMARY       |            1 | id
| A         |         796 |     NULL | NULL   |         |
| Transactions |          1 | Transactions1 |            1 | Ticket
| A         |        NULL |     NULL | NULL   |         |
| Transactions |          1 | Transactions2 |            1 | EffectiveTicket
| A         |        NULL |     NULL | NULL   |         |
+--------------+------------+---------------+--------------+----------------
-+-----------+-------------+----------+--------+---------+
3 rows in set (0.00 sec)

and


 show index from Attachments;
+-------------+------------+--------------+--------------+---------------+--
---------+-------------+----------+--------+---------+
| Table       | Non_unique | Key_name     | Seq_in_index | Column_name   |
Collation | Cardinality | Sub_part | Packed | Comment |
+-------------+------------+--------------+--------------+---------------+--
---------+-------------+----------+--------+---------+
| Attachments |          0 | PRIMARY      |            1 | id            | A
|         539 |     NULL | NULL   |         |
| Attachments |          1 | Attachments1 |            1 | Parent        | A
|        NULL |     NULL | NULL   |         |
| Attachments |          1 | Attachments2 |            1 | TransactionId | A
|        NULL |     NULL | NULL   |         |
| Attachments |          1 | Attachments3 |            1 | Parent        | A
|        NULL |     NULL | NULL   |         |
| Attachments |          1 | Attachments3 |            2 | TransactionId | A
|        NULL |     NULL | NULL   |         |
+-------------+------------+--------------+--------------+---------------+--
---------+-------------+----------+--------+---------+
5 rows in set (0.00 sec)

You should see something like the above.

If the indexes haven't been created, create them from the schema file
/usr/local/src/rt2/etc/schema.mysql

>
> can you point me to docs that talk about indexing the tables ? i haven't
used
> rt directly much yet(others on the network do) but i have been maintaining
> the 'back end' for a while.
>
> thanks!!
>
> nate
>
> --
> Nate Amsden
> System Administrator
> GraphOn
> http://www.graphon.com
>
> _______________________________________________
> 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
>
>