Last modified: 2012-08-26 14:40:02 UTC
Page Special:Wantedpages in Russian Wikipeda has links to existing articles. Example first item in the list ("Самоа").
The page is cached and refreshed from time to time. The operations needed to retrieve the data from the database are very expensive, so that we can't do this for each request.
One problem is that the articles that now exist are still shown in red with edit-action links. Anyway, I've regenerated this cached query, which took 13.09 seconds, compared to 0.99 seconds to get the previous cached query.
Who regularly refreshs the page? The page was cached more then 2 month.
The page was refreshed 2005-04-10 and since then is cached (today is 2005-04-25). What about "time to time" updates?
The page has been updated in the meantime. 'Самоа' is no longer #1, as can easily be seen. A script to perform more frequent updates is currently running, performance settings are being tested.
*** Bug 2092 has been marked as a duplicate of this bug. ***
(In reply to comment #2) > One problem is that the articles that now exist are still shown in red with > edit-action links. > ... That particular problem has since been reported in bug 1922.
"Этот список последний раз обновлялся в 18:53, 22 октября 2009. " "The following data is cached, and was last updated 18:53, 22 October 2009. " Yeah.... that's not good.
Putting bug 14786 in as a dependency.
*** Bug 38766 has been marked as a duplicate of this bug. ***
I'm sure these could be update every (say) 4 months without any impact in server performance whatsoever. That would be a *lot better* than not updating them ever.
If anyone can answer my, that would be great. If it can be turned on, that would be even better. ---- Special:Wantedpages hasn't been updated since 2009 on the Low Saxon Wikipedia (nds-nl), what is the reason for that, is it possible to turn this feature on? Someone has compiled a list in the past for the Low Saxon Wikipedia using a bot, unfortunately this user isn't active anymore. Is there someone who can help me with this?
*** This bug has been marked as a duplicate of bug 15434 ***