[Wikitech-l] Parser cache update/migration strategies

2014-09-09 Thread Daniel Kinzler
Hi all! tl;dr: How to best handle the situation of an old parser cache entry not containing all the info expected by a newly deployed version of code? We are currently working to improve our usage of the parser cache for Wikibase/Wikidata. E.g., We are attaching additional information related

Re: [Wikitech-l] Parser cache update/migration strategies

2014-09-09 Thread aude
On Tue, Sep 9, 2014 at 12:03 PM, Daniel Kinzler dan...@brightbyte.de wrote: Hi all! tl;dr: How to best handle the situation of an old parser cache entry not containing all the info expected by a newly deployed version of code? We are currently working to improve our usage of the parser

Re: [Wikitech-l] Parser cache update/migration strategies

2014-09-09 Thread Nikolas Everett
Also option 5 could be to continue without the days until the parser cash is invalidated on its own. Maybe option 6 could be to continue without the data and invalidate the cache and completely rerender only some of the time. Like 5% of the time for the first couple hours then 25% of the time for

Re: [Wikitech-l] Parser cache update/migration strategies

2014-09-09 Thread Daniel Kinzler
Am 09.09.2014 13:45, schrieb Nikolas Everett: All those options are less good then just updating the cache I think. Indeed. And that *sounds* simple enough. The issue is that we have to be sure to update the correct cache key, the exact one the OutputPage object in question was loaded from.

Re: [Wikitech-l] Parser cache update/migration strategies

2014-09-09 Thread Nikolas Everett
On Tue, Sep 9, 2014 at 8:00 AM, Daniel Kinzler dan...@brightbyte.de wrote: Am 09.09.2014 13:45, schrieb Nikolas Everett: All those options are less good then just updating the cache I think. Indeed. And that *sounds* simple enough. The issue is that we have to be sure to update the correct

Re: [Wikitech-l] Parser cache update/migration strategies

2014-09-09 Thread Tim Starling
On 09/09/14 22:00, Daniel Kinzler wrote: Sadly, the mechanism for determining the parser cache key is quite complicated and rather opaque. It's only as complicated as it has to be, to support the desired features: * Options which change the parser output. * Merging of parser output objects