Spellbook

Here you can find a list of the most important Web Development Resources, ordered by use, that can be filtered by programming language.

I was just skimming over Santos’ Post about SDO, and was saddened to see more anecdotes and less facts.

Here are two points that you should take note of:

• PDO is an “ultra fast direct layer to the database”.
• The benchmarks I think you’re referring to do not include the magic turbo switch I talk about here, that highlights performance problems when using prepared statements, which are on by default.

I’d love to see someone run some fair comparisons and publish the numbers.

Original post by wez+via_rss@netevil.org (Wez Furlong)

It’s really easy.

To dump the databases, use this from the system prompt:
mysqldump -uuser -ppassword database_name > filename.sql

To import, create the database and use this:
mysql -uuser -ppassword database_name < filename.sql

Have been reading some product literature on database scaling up and scaling out. Scaleup means scaling by moving to a bigger, more powerful server, while scaleout means scaling by adding more CPU boxes to a cluster of database servers.

SQL Server 2005

These are good introductory articles:

• Scaling Out SQL Server 2005
• Achieving Massive Scalability with SQL Server

Oracle 10g (RAC)

These are much more sophisticated articles. Also can you spot where Oracle 10g RAC beats SQL Server 2005 in scaleout?

• Oracle RAC Best Practices (pdf)
• Practical Guidance for Deploying Large Clusters
• Capacity Planning for Large Commodity Clusters (pdf)
• Performance Collection and Analysis in Large Clusters (pdf)
• Scale-up versus scale-out using Oracle 10g with HP StorageWorks Enterprise Virtual Arrays (pdf). This article is interesting, but is more about large data warehousing benchmarks (where the SuperDome shows its power), and not the typical workload of a web farm environment.
• Testing RAC Scalability on DELL is more representative of the workload in a web farm.

The typical technique used in MySQL for massive parallelism is the Continuous Replication method where a single master db server has read-write access to the database, and the data changes are replicated over to the other database servers, which are read-only. Does anyone know how stable PostgreSQL’s replication projects are and their current status?

Original post by PHP Everywhere - By John Lim