Daniel Mayer wrote:
It is important for our developers to have complete access
to the servers that
Wikimedia projects run on. Otherwise outages will be
significantly longer and
we would not have any way to fix things ourselves when it
is the server that
is the problem. Read only mirrors are a very real
possibility but in order to
get that to work we need somebody to code the
functionality. Jimbo supports
the idea of read only mirrors but somebody has to code that
to make it happen
in a near real time and seemless way. Any volunteers?
Me, me! :)
I've started working on DB replication. We should be able to set up a remote slave server once I'm done. The MySQL manual says you can even have slave servers connecting over a modem, just dialling up occasionally to get the latest updates. So having one in a different city or something shouldn't be a problem. There might be a few UI issues to sort out. I guess we'd have to set up a method of mirroring images too.
Sorry for my newbies question, but there's something i dont understand. Many web site around the world have only one DB server and many load balancing web server. Slashdot for example IIRC. Ok it must be a quadri processor... but it's very fast !
I'm not really sure, that pliny is the bottleneck.
The Larousse server is a piii866, it's a bit short for what we want to do I think. I hope the next upgrade will improve Larousse, then we'll can move other wikis to it. And we'll see if Pliny is really the bottleneck.
My 2 cents