Martin Edenhofer schrieb am Dienstag, 22. Juni 2004 um 10:10:56 +0200: > 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.
the problem disappeared after setting the charset to utf8, displaying the queue-view and switching back to iso-8859-15. the problem must be related to my charset-problems -- J�rg Friedrich There are only 10 types of people: Those who understand binary and those who don't. _______________________________________________ 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
