Tomasz Wegrzanowski wrote:
Mirroring is the biggest *disadvantage* of MySQL solution. UseMod wikis are extremely easy to efficiently mirror via rsync, and it was done with Phase I too. It was even easy to mirror it in "almost real-time" (like once an hour or so) over very small pipe (I did mirror Polish Wikipedia like that on 115kbit/s, and it took only small part of my bandwidth).
There is MySQL replication. I don't know much about it though (nor do I know much about rsync other than what it's used for), so I don't know.
MySQL can only produce full dumps, and they are huge, take lot of time to generate, and lot of time to import at the mirroring site.
I suppose I could argue that you could couple this with CVS, which can produce patches to the dumps, but that's getting hacky :-)
As far as queries are concerned, you can see it yourself on the Special Pages - most of the queries are turned off for performance reasons, so that's not really a good argument.
Ah, but that's not an indication that MySQL, or RDBMS in general, is a bad idea. I just shows that the current database schema is ill-designed.
And we need to update the data structures all the time for performance reasons.
I'm not sure I fully understand what you mean by this. Apparently we do update something like the "recentchanges" table on every edit, because some people seem to have thought that it would make for better performance, but I'm pretty much convinced that this assumption is fallacious. Updating that table on every edit, I believe, is more costly than the benefit it brings in reading it. I'll gladly let an expert correct me on this, but this is what my past experience told me.
Timwi