Comments on: 25 Point Basic MySQL Setup/Optimization Checklist

By: nima0102

nima0102 — Sun, 17 Oct 2010 12:46:25 +0000

Good Article
Thanks

By: Bill Getas

Bill Getas — Tue, 24 Aug 2010 09:33:01 +0000

point 15: “…for all intensive purposes…” ? You write like one who paid more attention to computerese and warez than to English. FOR ALL INTENTS AND PURPOSES

By: Daily Digest for 2009-07-24 | Pedro Trindade

Daily Digest for 2009-07-24 | Pedro Trindade — Sat, 25 Jul 2009 07:17:47 +0000

[...] Bookmarked a link on Delicious. SayNoToFlash » 25 Point Basic MySQL Setup/Optimization Checklist [...]

By: Website Optimization

Website Optimization — Thu, 23 Jul 2009 15:20:21 +0000

Thanks for the great article. Truely a comprehensive list of ways to optimize a database which ultimately results in faster websites. I was not aware of the case sensitive option available – will have to try it out.
I will also add some bad designed db practice of storing the number of hits as a column of the same record – this makes every read awrite which sucks in performance.

By: jestep

jestep — Wed, 22 Jul 2009 15:44:51 +0000

That’s a good point.

My only argument would be that user contributed data is only going to end up in a few specific columns, so you would most likely know exactly what tables/columns to allow UTF-8.

However, that also brings up whether it is a good idea to mix collations on a database, which can end up being a nightmare as well.

By: Peter

Peter — Wed, 22 Jul 2009 09:26:36 +0000

I disagree with #7. These days it’s impossible to predict when you may need to store multibyte data in a database, so I always go for utf-8 throughout from the start – itsaves painful days of converting the collation later when the client’s inserted records in Arabic/Chinese/Russian and the data’s screwed when they come to extract it.