Page MenuHomePhabricator

Investigate: Cache processed text
Closed, ResolvedPublic4 Estimated Story Points


Text that has been processed (cleaned and segmented) should be cached and not processed again, unless the it has been altered. It's is possible that this type of caching is already done by MediaWiki (see

Event Timeline

Lokal_Profil added a subscriber: Lokal_Profil.

Based on need in T151786

Lokal_Profil set the point value for this task to 1.Nov 30 2016, 2:22 PM

First thought on test:

  • Two different browsers visiting one after another. Only the first should trigger the log message in cleaner/segmenter.
  • Second user updates page content. Log should trigger once for the second user.

If passes then all is well. If not then investigate various caching settings/mechanisms in MediaWiki and set up a task for implementation.

Lokal_Profil renamed this task from Cache processed text to Investigate: Cache processed text.Nov 30 2016, 2:22 PM

Should await T153841 which will most likely affect any assumptions here.

Sebastian_Berlin-WMSE lowered the priority of this task from Low to Lowest.Feb 7 2017, 2:36 PM
Sebastian_Berlin-WMSE changed the point value for this task from 1 to 4.Feb 7 2017, 2:44 PM

Changed story points to new system

Sebastian_Berlin-WMSE raised the priority of this task from Lowest to Low.Sep 20 2017, 1:56 PM