Quantcast
Channel: DOCU - Foren
Viewing all articles
Browse latest Browse all 6544

Administration - Installation - Core: Re: Update 5.3 -> 5.4, database step 5336 is very slow

$
0
0
The problem is, that the query which determines the value for the field "first_login" is highly unoptimized. It joins the tables usr_data and read_event using no indexes at all. If you have a larger database, consisting of thousands of users and maybe millions of read events, this will take a LOT of time.

A workaround for this is introducing a temporary index in mysql, which speeds up the query in the update step 5336 tremendously:

CREATE INDEX foo ON read_event(usr_id);

After the update you may want to remove this index again:

DROP INDEX foo ON read_event;

Edit: I opened a bug report in Mantis, since I suspect there will be a lot of larger installations out there that will face the same issue: https://docu.ilias.de/goto_docu_frm_1875_5832.html

Viewing all articles
Browse latest Browse all 6544

Trending Articles