Bug #20910
closedspeed up list module by improving internal handling of localisations
0%
Description
Problem:
The handling of translations in the list module (localization view) is inefficient.
2 SQL queries will be executed to find existing localisations and for showing the localisation panel. Both queries are basically the same, only the selected fields are changed. Additionally the list module instantiates a new object of class.t3lib_transl8tools for each record which is shown in the list.
class t3lib_transl8tools is initiated in exactly the same way each time (no constructor or other changing vars)
Solution:
Make only one query to find localizations and re-use the result.
initialize class transl8tools only once in function start() in class.db_list.inc and re-use it.
Benchmarks:
time for displaying a list of 100 records (single table view, Localization view=1). Page has 2 alternative page languages
trunk = ~115ms
patched = ~97ms
measured in class.db_lis.inc function generatedList()
(issue imported from #M11764)
Files
Updated by Rupert Germann about 15 years ago
attached patch "11764_followup2.diff" fixes the problems in extensions which use their own page-module.
committed followup2 to trunk, rev 6424
thanks Steffen