On 23 Jan 2003, Brion Vibber wrote: Part of the problem might be MySQL. It is very fast for applications that are entirely static, however, when the data are being changed, it is quite slow. In particular, MySQL scales very poorly to multiple users trying to simultaneously update the database. I see from the statistics that the typical Wikipedia page is read only 4 or 5 times for each time it is updated. For such a use profile, PostgreSQL is likely to offer better performance. Of course, the only benchmark that counts is the application at hand. Has anyone tried Wikipedia on PostgreSQL? Apologies if I've strayed off topic, M Carling

On Fri, Jan 24, 2003 at 12:36:58AM -0800, Brion Vibber wrote: Don't get pissy, Brion. mod_wiki is en route. You won't see most of the advantages of Postgres without redesigning the database schema to take advantage of it. Yes, but not as frustrating as trying to actually dive in and make such a patch; the MySQLisms and the fact the SQL statements are created on the fly instead of isolated into one easily modifiable file, the way the Scoop codebase does, makes it very difficult. I agree; if you have the stamina for it, please provide a patch so we can see how Postgres supports Wikipedia as it stands right now. mod_wiki is a fourth generation thing, while the current codebase is third generation. Jonathan -- Geek House Productions, Ltd. Providing Unix & Internet Contracting and Consulting, QA Testing, Technical Documentation, Systems Design & Implementation, General Programming, E-commerce, Web & Mail Services since 1998 Phone: 604-435-1205 Email: djw(a)reactor-core.org Webpage: http://reactor-core.org Address: 2459 E 41st Ave, Vancouver, BC V5R2W2