Change Details

As seen in the report below it appears as `Scribunto_LuaSandboxCallback::addStatementUsage` is taking a considerable amount of computation time lately. A 6 Hour Timebox is required to investigate: # What is causing this function to take longer lately? # Can we continuously monitor this to be alerted to similar changes in the future? (Optional, can be potentially separated into a separate task) **Initial Report:** > The computing times increased drastically by about 100 %, mainly produced by a drastic increase of the computing time of the Lua function addStatementUsage (increase of about 500 %). > > From the Lua profile of https://de.wikivoyage.org/wiki/Halle_(Saale) (see html source code): > > > ``` > Lua Profile: > Scribunto_LuaSandboxCallback::addStatementUsage 4540 ms 55.0% > Scribunto_LuaSandboxCallback::callParserFunction 1640 ms 19.9% > Scribunto_LuaSandboxCallback::getEntity 540 ms 6.5% > Scribunto_LuaSandboxCallback::addSiteLinksUsage 420 ms 5.1% > Scribunto_LuaSandboxCallback::getEntityStatements 320 ms 3.9% > init <Modul:CountryData/Geography> 100 ms 1.2% > recursiveClone <mwInit.lua:41> 100 ms 1.2% > ? 100 ms 1.2% > Scribunto_LuaSandboxCallback::gsub 80 ms 1.0% > init <Modul:VCard/Subtypes> 80 ms 1.0% > [others] 340 ms 4.1% > ``` > Maybe it is the same like T236485.

As seen in the report below it appears as `Scribunto_LuaSandboxCallback::addStatementUsage` is taking a considerable amount of computation time lately. A 6 Hour Timebox is required to investigate: # What is causing this function to take longer lately? # Can we continuously monitor this to be alerted to similar changes in the future? (Optional, can be potentially separated into a different task) **Initial Report:** > The computing times increased drastically by about 100 %, mainly produced by a drastic increase of the computing time of the Lua function addStatementUsage (increase of about 500 %). > > From the Lua profile of https://de.wikivoyage.org/wiki/Halle_(Saale) (see html source code): > > > ``` > Lua Profile: > Scribunto_LuaSandboxCallback::addStatementUsage 4540 ms 55.0% > Scribunto_LuaSandboxCallback::callParserFunction 1640 ms 19.9% > Scribunto_LuaSandboxCallback::getEntity 540 ms 6.5% > Scribunto_LuaSandboxCallback::addSiteLinksUsage 420 ms 5.1% > Scribunto_LuaSandboxCallback::getEntityStatements 320 ms 3.9% > init <Modul:CountryData/Geography> 100 ms 1.2% > recursiveClone <mwInit.lua:41> 100 ms 1.2% > ? 100 ms 1.2% > Scribunto_LuaSandboxCallback::gsub 80 ms 1.0% > init <Modul:VCard/Subtypes> 80 ms 1.0% > [others] 340 ms 4.1% > ``` > Maybe it is the same like T236485.

As seen in the report below it appears as `Scribunto_LuaSandboxCallback::addStatementUsage` is taking a considerable amount of computation time lately. A 6 Hour Timebox is required to investigate: # What is causing this function to take longer lately? # Can we continuously monitor this to be alerted to similar changes in the future? (Optional, can be potentially separated into a separatedifferent task) **Initial Report:** > The computing times increased drastically by about 100 %, mainly produced by a drastic increase of the computing time of the Lua function addStatementUsage (increase of about 500 %). > > From the Lua profile of https://de.wikivoyage.org/wiki/Halle_(Saale) (see html source code): > > > ``` > Lua Profile: > Scribunto_LuaSandboxCallback::addStatementUsage 4540 ms 55.0% > Scribunto_LuaSandboxCallback::callParserFunction 1640 ms 19.9% > Scribunto_LuaSandboxCallback::getEntity 540 ms 6.5% > Scribunto_LuaSandboxCallback::addSiteLinksUsage 420 ms 5.1% > Scribunto_LuaSandboxCallback::getEntityStatements 320 ms 3.9% > init <Modul:CountryData/Geography> 100 ms 1.2% > recursiveClone <mwInit.lua:41> 100 ms 1.2% > ? 100 ms 1.2% > Scribunto_LuaSandboxCallback::gsub 80 ms 1.0% > init <Modul:VCard/Subtypes> 80 ms 1.0% > [others] 340 ms 4.1% > ``` > Maybe it is the same like T236485.