Marcin,
It's the biggest and most heavily trafficked of our wikis because its the
English-language version of the wiki. We also have German, French, and
Spanish, but the English-speaking community is by far the largest and most
active. There are some tiny configuration differences between the wikis
(e.g. the value of $wgJobRunRate, the specific extensions loaded) but
nothing very significant I don't believe.
I should also add that all four of these wikis (we have a 5th, for 7 total,
not 6 as I'd originally said) also use Semantic MediaWiki extensively. I
believe the other three wikis would run into the same problem if they had
same amount of traffic as the English one. However, since they all are
vhosts within the same Apache instances, the English one's problems affect
all of them.
Justin
On Thu, Nov 12, 2015 at 1:42 AM, Marcin Cieslak <saper(a)saper.info> wrote:
On 2015-11-12, Justin Lloyd
<jlloyd.wiki(a)gmail.com> wrote:
* Six wikis are configured as Vhosts in Apache,
load balanced by a
separate
set of front-end servers, where two of the wikis
are for private internal
use and the other four are public, though the traffic to one of the
public
wikis dwarfs the rest and it's the wiki
giving me problems.
(...)
I'm mainly looking right now for how to
troubleshoot the stuck processes,
but any advice regarding this architecture is also welcome, as I feel it
could use some improvement but I'm not sure how just yet.
The question that immediately comes to my mind before I start digging
any further - how is the wiki making problems special? Is it just getting
most of the traffic (it is the "most interesting" one) or is its
configuration slightly different?
Marcin Cieślak
https://www.mediawiki.org/wiki/User:Saper
_______________________________________________
MediaWiki-l mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l