Extrem lange Ladezeiten von großen Tickets...

[OTRS_hil]

Hallo,

wir haben das Problem, dass bei grossen Tickets (also mehr als 200 Einträge im Ticket) die Ladezeiten extrem langsam sind.
Aktuell ca. 10 Minuten für ein Ticket mit 290 entries.
Im Logfile kann ich soweit nichts erkennen - ist das vllt. ein "bekanntes" Problem und gibt es dafür vllt. irgendwelche Tuningmöglichkeiten ?
Bitte Info.

Gruß

[Andre Bauer]

http://doc.otrs.org/2.4/en/html/c2745.html

http://wiki.mobbing-gegner.de/Linux/MySql/optimieren

http://github.com/rackerhacker/MySQLTuner-perl

http://www.day32.com/MySQL/

[jojo]

Du solltest vielleicht noch Ticket::Frontend::TicketArticleFilter anschalten, um nicht benötigte Artikeltypen bei Bedarf auszublenden.

[OTRS_hil]

Hallo,

so habe soweit alle Einstellungen überprüft, aber komme zu dem Ergebnis, dass das Problem wohl beim Aufbereiten der Daten im OTRS liegt.
Hier ein kleiner Auszug aus dem Mysql.log: (bitte dazu auf die Zeiten schauen)
100120 12:15:19 5 Query SELECT user_id, preference_period, date_start, date_end, weekly_hours, leave_days, overtime FROM time_accounting_user_period WHERE date_start <= '2010-01-20 00:00:00' AND date_end >='2010-01-20 00:00:00' AND status = '1'
5 Query SELECT sa.ticket_id, sa.a_from, sa.a_to, sa.a_cc, sa.a_subject, sa.a_reply_to, sa.a_message_id, sa.a_in_reply_to, sa.a_references, sa.a_body, st.create_time_unix, st.ticket_state_id, st.queue_id, sa.create_time, sa.a_content_type, sa.create_by, st.tn, article_sender_type_id, st.customer_id, st.until_time, st.ticket_priority_id, st.customer_user_id, st.user_id, st.responsible_user_id, sa.article_type_id, sa.a_freekey1, sa.a_freetext1, sa.a_freekey2, sa.a_freetext2, sa.a_freekey3, sa.a_freetext3, st.ticket_answered, sa.incoming_time, sa.id, st.freekey1, st.freetext1, st.freekey2, st.freetext2, st.freekey3, st.freetext3, st.freekey4, st.freetext4, st.freekey5, st.freetext5, st.freekey6, st.freetext6, st.freekey7, st.freetext7, st.freekey8, st.freetext8, st.freekey9, st.freetext9, st.freekey10, st.freetext10, st.freekey11, st.freetext11, st.freekey12, st.freetext12, st.freekey13, st.freetext13, st.freekey14, st.freetext14, st.freekey15, st.freetext15, st.freekey16, st.freetext16, st.ticket_lock_id, st.title, st.escalation_update_time, st.freetime1 , st.freetime2, st.freetime3, st.freetime4, st.freetime5, st.freetime6, st.type_id, st.service_id, st.sla_id, st.escalation_response_time, st.escalation_solution_time, st.escalation_time, st.change_time FROM article sa, ticket st WHERE sa.id = '62587' AND sa.ticket_id = st.id ORDER BY sa.create_time, sa.id ASC
5 Query SELECT name FROM ticket_type WHERE id = '1' LIMIT 1
5 Query SELECT login FROM users WHERE id = '3'
5 Query SELECT login FROM users WHERE id = '37'
5 Query SELECT name FROM ticket_priority WHERE id = '5'
5 Query SELECT name FROM ticket_lock_type WHERE id = '2'
5 Query SELECT name FROM service WHERE id = '2' LIMIT 1
5 Query SELECT name FROM sla WHERE id = '2' LIMIT 1
5 Query SELECT q.name, q.group_id, q.unlock_timeout, q.system_address_id, q.salutation_id, q.signature_id, q.comments, q.valid_id, q.first_response_time, q.first_response_notify, q.update_time, q.update_notify, q.solution_time, q.solution_notify, q.follow_up_id, q.follow_up_lock, sa.value0, sa.value1, q.id, q.default_sign_key, q.calendar_name FROM queue q, system_address sa WHERE q.system_address_id = sa.id AND q.id = '28'
5 Query SELECT ts.id, ts.name, ts.valid_id, ts.comments, ts.type_id, tst.name, ts.change_time, ts.create_time FROM ticket_state ts, ticket_state_type tst WHERE ts.type_id = tst.id AND ts.id = '6'
5 Query SELECT id, name, calendar_name, first_response_time, first_response_notify, update_time, update_notify, solution_time, solution_notify, valid_id, comments, create_time, create_by, change_time, change_by , type_id, min_time_bet_incidents FROM sla WHERE id = '2' LIMIT 1
5 Query SELECT id, name FROM general_catalog WHERE general_catalog_class = 'ITSM::SLA::Type' AND valid_id = 1
5 Query SELECT service_id FROM service_sla WHERE sla_id = '2' ORDER BY service_id ASC
5 Query SELECT name FROM article_sender_type WHERE id = '3'
5 Query SELECT name FROM article_type WHERE id = '2'
5 Query SELECT st.id, st.queue_id, sq.name, st.ticket_state_id, st.ticket_lock_id, sp.id, sp.name, st.create_time_unix, st.create_time, sq.group_id, st.tn, st.customer_id, st.customer_user_id, st.user_id, st.responsible_user_id, st.until_time, st.freekey1, st.freetext1, st.freekey2, st.freetext2, st.freekey3, st.freetext3, st.freekey4, st.freetext4, st.freekey5, st.freetext5, st.freekey6, st.freetext6, st.freekey7, st.freetext7, st.freekey8, st.freetext8, st.freekey9, st.freetext9, st.freekey10, st.freetext10, st.freekey11, st.freetext11, st.freekey12, st.freetext12, st.freekey13, st.freetext13, st.freekey14, st.freetext14, st.freekey15, st.freetext15, st.freekey16, st.freetext16, st.freetime1, st.freetime2, st.freetime3, st.freetime4, st.freetime5, st.freetime6, st.change_time, st.title, st.escalation_update_time, st.timeout, st.type_id, st.service_id, st.sla_id, st.escalation_response_time, st.escalation_solution_time, st.escalation_time FROM ticket st, ticket_priority sp, queue sq WHERE sp.id = st.ticket_priority_id AND sq.id = st.queue_id AND st.id = '5444' LIMIT 1
5 Query SELECT group_id FROM queue WHERE id = '28' LIMIT 1
5 Query SELECT id FROM valid WHERE name = 'valid'
5 Query SELECT g.id, g.name, gu.permission_key, gu.permission_value, gu.user_id FROM groups g, group_user gu WHERE g.valid_id IN (1) AND g.id = gu.group_id AND gu.permission_value = 1 AND gu.permission_key IN ( 'ro','rw' ) AND gu.user_id = 2
5 Query SELECT ru.role_id, ru.user_id, r.name FROM role_user ru, roles r WHERE r.valid_id IN (1) AND r.id = ru.role_id AND ru.user_id = 2
5 Query SELECT g.id, g.name, gu.permission_key, gu.permission_value, gu.role_id FROM groups g, group_role gu WHERE g.valid_id IN (1) AND g.id = gu.group_id AND gu.permission_value = 1 AND gu.permission_key IN ( 'ro','rw' ) AND gu.role_id IN (1,10,12,13,14,15,16,17,18,19,20,21,22,23,25,27,28,3,5,6,8)
5 Query SELECT content_path FROM article WHERE id = '62587'
>>> Bis hier hin dauert das ganze ungefähr 5 Sekunden... Danach benötigt OTRS über 2 Minuten für das Aufbereiten der Daten ??
siehe...
100120 12:17:45 5 Quit

Habe soweit alles überprüft - wie gesagt, muss am/im OTRS liegen....

Bitte Info, wenn möglich....

[jojo]

Dein Browser wird ein Großteil der Ladezeiten verursachen, da die Seite aus miteinander verschachtelten Tabellen besteht...