
July 30th, 2000, 12:03 AM
|
|
Gödelian monster
|
|
Join Date: Jul 1999
Location: Pembroke Pines, Florida, USA
|
|
|
I can't give you any statistical results, but my experience with MySQL has been:
1. I have never seen it hit a serious bottleneck on ANY of my production or development servers. (one of my development servers was a Pentium 90 with 16 MB RAM running FreeBSD, and I was able to develop a complete e-commerce application on it without any noticeable drag in searching through thousands of records.)
2. It may not have transactions (commit/rollback), but I have never seen MySQL corrupt a table, even from random reboots.
3. The benchmarks I have seen generally show one thing: MySQL is the fastest way to serve out data to a dynamic website. It may not have the best performance in INSERTS, UPDATES, or some of the more complex operations, but for simply serving out data, (especially with many hits using simple queries), nothing is faster.
4. By the time you are ready to move to Oracle or Informix, you may not want to. MySQL 3.23.xx is almost out of beta, and will support many more complex operations than previous versions, including transactions, subqueries, etc... AND it will support table sizes in the multi-terabyte range. You might even want to start your development with version 3.23.21, which is a fairly stable beta version.
5. On the other hand, you just might want to check out PostgreSQL, which is already much more sophisticated (if not quite as fast) than MySQL.
|