This would allow them to be run in parallel, yes. Being in separate
databases means extra last-minute checks for existence or security (CYA for
if deletes get missed) are skipped as interwiki links are generated, but
overall not a big deal and an expected loss as part of the interwiki search.
On W
Recently, the Team Practices Group agreed to a set of norms around how that
team will use IRC[1].
Would it be helpful for Discovery to agree on its own IRC norms? They could
end up being quite different from what TPG decided on. But whatever we
decided on, it seems like it would be helpful to know
Hey all,
After a longer-than-expected deployment process to fix a couple of
bugs, I'm pleased to report all the backfilling is done and we have a
new version of the dashboard out. Amongst other things, this includes
a fix to a bug whereby the KPI infoboxes were displaying the wrong
values - thanks
Would this help if we wanted to simultaneously search multiple wikis, or
are those in separate databases so it would have no effect?
Kevin Smith
Agile Coach, Wikimedia Foundation
On Wed, Sep 9, 2015 at 5:18 AM, David Causse wrote:
> Thanks Erik!
>
> This is very promising and it opens a lot o
Thanks Erik!
This is very promising and it opens a lot of new possibilities.
Guessing the gain is pretty hard but I think we run many small requests
where network overhead is quite high compared to the actual work done by
elastic. This would definitely help.
Le 08/09/2015 21:01, Erik Bernhard
