2010/8/1 Aryeh Gregor <Simetrical+wikilist(a)gmail.com>om>:
On Sun, Aug 1, 2010 at 4:43 PM, Roan Kattouw
<roan.kattouw(a)gmail.com> wrote:
He can't, but I can. I ran a couple of
queries and put the result at
http://www.mediawiki.org/wiki/User:Catrope/Stub_threshold
I can too -- I'm a toolserver root, so I have read-only access to
pretty much the whole database (minus some omitted
databases/tables/columns, mainly IP addresses and maybe private
wikis).
Ah yes, I forgot about that. I was assuming you'd need access to the
live DB for this.
But no need, since you already did it. :) The data
isn't
complete because not all users have been ported to user_properties,
right?
I don't know. Cursory inspection seems to indicate user_properties is
relatively complete, but comprehensive count queries are too slow for
me to dare run them on the cluster. Maybe you could run something
along the lines of SELECT COUNT(DISTINCT up_user) FROM
user_properties; on the toolserver and compare it with SELECT COUNT(*)
FROM user;
One easy hack to reduce this problem is just to only
provide a few
options for stub threshold, as we do with thumbnail size. Although
this is only useful if we cache pages with nonzero stub threshold . .
. why don't we do that? Too much fragmentation due to the excessive
range of options?
Maybe; but the fact that the field is present but set to 0 in
the
parser cache key is very weird. SVN blame should probably be able to
tell who did this and hopefully why.
Roan Kattouw (Catrope)