Hi J�rg,
On Tue, Jun 22, 2004 at 07:59:09AM +0200, Joerg Friedrich wrote:
> yesterday I tried to get the reason of these problems, because I noticed
> that otrs is only slow for my account, no other user has the same
> problems.
> [...]
>
> 2. the heavy load the machine has, when I access the queue view is a db
> problem. I use postgres. Number of tickets ~7000.
>
> I tracked this down to this query:
> SELECT t.id, a.article_sender_type_id, a.incoming_time,
> q.escalation_time, a.id, t.ticket_priority_id FROM article a, queue q,
> ticket t WHERE t.ticket_answered != 1 AND q.escalation_time != 0
> AND t.ticket_state_id in ( 1, 4, 6, 7, 8 ) AND t.id = a.ticket_id
> AND q.id = t.queue_id AND q.group_id IN ( 2, 3, 4, 10, 1, 12, 7,6 )
> AND t.ticket_lock_id in ( 1, 3 ) ORDER BY t.id, t.ticket_priority_id
> DESC, a.incoming_time LIMIT 1500
>
> postgres needed ~15 sec to perform it.
> removing one queue from my rw-queues, and the query is done in less than
> a second.
>
> this is a postgres problem.
Maybe a postgres problem or we could optimize the SQL query.
PS: It's because postgres gets problems with many open ticksts. It should
work fine if there are ~ 1000 open tickets.
> --
> J�rg Friedrich
Martin Edenhofer
--
((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg
http://www.otrs.de/ :: Manage your communication!
_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
