Change Details

WANCache does not allow for passing WRITE_ALLOW_SEGMENTS, which means that large preprocessor cache entries cannot be stored. An example of large parser output entries was found during unrelated debug log entries for RefreshLinksJob failures at T307133.

While BagOStuff supports the storing of large values (>1mb) in memcached using WRITE_ALLOW_SEGMENTS, the WANObjectCache class does not support it yet. Since the preprocessor text was changed to use WANCache, large wiki pages will not benefit from caching since the cache writes will fail. The preprocessor cache is useful for expanding templates during parser cache misses (e.g. on edit or for users with non-standard preferences). An example of large parser output entries was found during unrelated debug log entries for RefreshLinksJob failures at T307133. We should: * [x] Add a "segmentable" option to WANCache that uses WRITE_ALLOW_SEGMENTS * [] Support * [] Use the new option in PreprocessorHash::preprocessToObj()

WANCache does not allow for passing WRITE_ALLOW_SEGMENTS,hile BagOStuff supports the storing of large values (>1mb) in memcached using WRITE_ALLOW_SEGMENTS, the WANObjectCache class does not support it yet. Since the preprocessor text was changed to use WANCache, large wiki pages will not benefit from caching since the cache writes will fail. The preprocessor cache is useful for expanding templates during parser cache misses (e.g. which means that large preprocessor cache entries cannot be storedon edit or for users with non-standard preferences). An example of large parser output entries was found during unrelated debug log entries for RefreshLinksJob failures at T307133. We should: * [x] Add a "segmentable" option to WANCache that uses WRITE_ALLOW_SEGMENTS * [] Support * [] Use the new option in PreprocessorHash::preprocessToObj()