Comments on: High Performance MySQL: Optimization, Backups, Replication, and More

By: F. Levanti

F. Levanti — Fri, 19 Feb 2010 21:30:42 +0000

A good book for developers that want more. They want to optimize their scripts and really understand how MYSQL works also behind the scene.

A must have book

Rating: 5 / 5

By: Lucas de L. Lorenzo

Lucas de L. Lorenzo — Fri, 19 Feb 2010 20:29:31 +0000

It’s a good start point into high performance tunning, but not a deep into every concept, which is not possible in a single book. The book dives into some benchmark, optimization of queries, the capabilities of every storage engine, and also its weaknesses, some compared backup strategies, replication, and master-slave configurations, all well explained, up to MySQL 5.1, but with new versions in mind. I enjoy this book, although some concerns are hard by nature, and some kind of query optimization could be more graphical to better understanding.
Rating: 4 / 5

By: Marinko Tarlac

Marinko Tarlac — Fri, 19 Feb 2010 19:19:42 +0000

Very nice book but unfortunately this book is not for beginners so if you’re new in databases try to read some tutorials or books for beginners and then come back for this book.

Rating: 5 / 5

By: William B. Harding

William B. Harding — Fri, 19 Feb 2010 17:58:11 +0000

I bought this book hoping to get a detailed understanding of how to best create and use indexes for my high traffic web site. While the book does a great job of covering the pros and cons of standard indexes, it devotes only a single page to the utility of index_merge (introduced in Mysql 5.0). Combined with a general dearth of information about index_merge on the web, this was a really disappointment, since index_merge seems to afford the possibility of using multiple, smaller indexes, rather than smaller number of bulky indexes (as this book recommends).

In my eyes, a thorough analysis of indexing techniques in Mysql 5+ must discuss the strategic opportunities afforded by index_merge. It would seem to me that this gives the developer the ability to simply index the fields they want indexed, without having to sweat left-precedence of combined indexes or trying to make long indexes that include all of the possibly needed indexes in an order that will satisfy all possible query combinations.

If limitations to the utility of index_merge make some of these possibilities not feasible, the book ought to at least give a rundown of the pros and cons of index_merge vs. compound indexes.

The near-total omission of a new feature that could have profound implications upon the most optimal way to query & index makes me recommend this book with a tablespoon of salt. Rating: 3 / 5

By: Rahul Jaiswal

Rahul Jaiswal — Fri, 19 Feb 2010 16:50:59 +0000

The book is good. lots of new information as compared to the previous edition.

the book arrived in time.
Rating: 4 / 5