Last modified: 2014-02-12 23:53:37 UTC
I was trying to look at MobileFrontend today, but i was getting timeouts because the device parser needs to work through the WURFL database the first time it runs I suspect. On my wiki that was continuously failing due to max_execution_time. Such an intensive job should probably be thrown on the job queue.
Job queue wouldn't be suitable, as there'd be nothing to do until it was complete. It should probably be preprocessed and only the useful bits retained & distributed with source, as with our Unicode conversion & normalization tables.
Not really sure what to do with this bug. There are about 13,969 files needed in the cache for WURFL to work correctly. I don't really know that we want this in our repository. I'm researching switching to memcache for the storage vs. the file based cache.
(In reply to comment #2) > I'm researching switching to memcache for the storage vs. the file based cache. For the purposes of an extension that is used by more than WikiFarms like Wikimedia, it would be good to provide some sort of pre-parsed PHP like Brion is talking about.
I'm still researching what will be the best solution for this issue. I'll update the bug once I've got some ideas.
Can we just init cache from a command-line script?
No more WURFL === no more slow startup.
