Comments on: Wikipedia: site internals, etc (the workbook)

By: goarilla

goarilla — Tue, 03 Mar 2009 08:00:18 +0000

The biggest problem with distributed file systems, is that they don’t really exist in opensource world (and MogileFS isn’t that distributed either, nor easy to maintain/extend).

what about lustre ?

By: Fox

Fox — Sat, 31 May 2008 12:08:32 +0000

Hi,

The pdf is useful! Thanks!

I have some questions,

1. Will wikipedia’s config files such as httpd.conf, my.cnf, squid.conf be shared in the future? [of coz sensitive info such as IP can be masked!],
I really want to look into it to learn the optimization being used.

2. Are there any URL I can download the internal scripts being used in wikipedia?

THanks.

By: rubriche » Blog Archive » L’architettura di Wikipedia nel dettaglio [Simone Carletti’s Blog]

Mon, 03 Sep 2007 08:54:34 +0000

[...] Mituzas, che lavora per MySQL AB e Wikipedia, ha pubblicato un interessante workbook sull’architettura interna dei server della famosa enciclopedia. Sempre dal post di Domas scopro che un altro interessante whitepaper pubblicato illustra [...]

By: Сергей Куракин » Исследования Load Balancing и Performance для сайтов

Сергей Куракин » Исследования Load Balancing и Performance для сайтов — Tue, 14 Aug 2007 15:10:23 +0000

[...] Domas Mituzas – специалист по MySQL + поддержка Wikipedia рекомендую Wikipedia: site internals, etc (the workbook) Load Balancing Your Web Site Performance Tuning Best Practices for MySQL MySQL Manual Index Hint [...]

By: Wikipedian arkkitehtuuri « dippaa ja elämää

Wikipedian arkkitehtuuri « dippaa ja elämää — Mon, 21 May 2007 10:39:55 +0000

[...] Artikkeli domasin blogissa [...]

By: Domas Mituzas

Domas Mituzas — Mon, 14 May 2007 09:09:15 +0000

Mark, that strikes you out!

By: Mark

Mark — Mon, 14 May 2007 08:58:28 +0000

> And every Wikipedia tech person knows how to handle MySQL replication ;-)

I don’t!

By: Domas Mituzas

Domas Mituzas — Fri, 11 May 2007 12:07:40 +0000

External storage of media is not handled by mysql replication setups, just revision texts – they have to be accessed by application, so using common layers (Database class, LoadBalancer, etc) are easier than to using ‘distributed file system’.

The biggest problem with distributed file systems, is that they don’t really exist in opensource world (and MogileFS isn’t that distributed either, nor easy to maintain/extend).

If there’d be efficient distributed storage, we would use it.
And every Wikipedia tech person knows how to handle MySQL replication ;-)

By: Paul Annesley

Paul Annesley — Fri, 11 May 2007 12:03:05 +0000

Great – thanks very much for posting this extremely valuable information on scalable architecture. It’s precisely the kind of information I’ve been looking for, and I’m sure it will be invaluable to many others too.

I’m interested to see that external storage of files is handled by small mysql replication setups on the application servers – was this chosen over some kind of distributed filesystem for any reasons other than simplicity?

By: Robert Accettura’s Fun With Wordage » Blog Archive » Wikipedia Infrastructure

Mon, 30 Apr 2007 02:32:53 +0000

[...] a great read on Wikipedia’s Infrastructure. Two excellent sets of slides. A lot can be done with a LAMP stack. The common theme: caching and [...]

By: Rob Church

Rob Church — Sun, 29 Apr 2007 19:55:40 +0000

Good read. The first few pages are a load of CARP, but it picks up. ;)