20 tips for MySQL db architects

#1

Post by nocivus » Mon, Oct 20, 2008, 9:29 AM UTC

20 tips for MySQL db architects
scribd.com

Re: 20 tips for MySQL db architects

#2

Post by axod » Mon, Oct 20, 2008, 3:39 PM UTC

Obligatory complaint about how scribd takes 5 minutes to load and ends up as a worse user experience than linking to the pdf.

Wait 5 minutes, then click on 'download'. sigh

Re: 20 tips for MySQL db architects

#3

Post by Freaky » Mon, Oct 20, 2008, 4:21 PM UTC

    ❖Average 25% - 30% saving on engagements
    ❖Better 60% (200GB System)
    ❖Best 78% (8GB per master with 12 masters)

What are they wibbling about?

Re: 20 tips for MySQL db architects

#4

Post by tialys » Mon, Oct 20, 2008, 5:06 PM UTC

This seems like it could be really handy if someone could perhaps narrate along with it and help me understand what all of his talking points are about.

Re: 20 tips for MySQL db architects

#5

Post by tocomment » Mon, Oct 20, 2008, 5:25 PM UTC

Why does he say varchar(255) is bad design?

Re: 20 tips for MySQL db architects

#6

Post by ronaldbradford » Mon, Oct 20, 2008, 5:32 PM UTC

axod wrote: post #2

Obligatory complaint about how scribd takes 5 minutes to load and ends up as a worse user experience than linking to the pdf. Wait 5 minutes, then click on 'download'. sigh

axod, you can download these slides and other MySQL related presentations directly from http://ronaldbradford.com/presentations/

Re: 20 tips for MySQL db architects

#7

Post by ronaldbradford » Mon, Oct 20, 2008, 5:33 PM UTC

tialys wrote: post #4

This seems like it could be really handy if someone could perhaps narrate along with it and help me understand what all of his talking points are about.

A video of the presentation can be found at http://technocation.org/node/533/play

Re: 20 tips for MySQL db architects

#8

Post by petercooper » Mon, Oct 20, 2008, 5:37 PM UTC

tocomment wrote: post #5

Why does he say varchar(255) is bad design?

Because 255 is now just an arbitrary choice for a VARCHAR length.

Explanation: Prior to MySQL 5.0.3 (give or take a few point releases - I forget) a VARCHAR column could be 255 characters in length maximum, so VARCHAR(255) was often used as a default. Now, however, you can go up to 65,535 characters on VARCHAR, so if you're still using "255" then that seems arbitrary and not well thought out (or your schema is just old).

Re: 20 tips for MySQL db architects

#9

Post by ronaldbradford » Mon, Oct 20, 2008, 5:42 PM UTC

Freaky wrote: post #3

❖Average 25% - 30% saving on engagements ❖Better 60% (200GB System) ❖Best 78% (8GB per master with 12 masters) What are they wibbling about?

As a database architect expert, I generally average a 25-30% reduction in the Disk Footprint of the database, sometimes with zero impact for application changes.

I use a very simple equation. DISK = MEMORY = PERFORMANCE Reducing the size of the disk footprint, and therefore the amount of disk reads (disk is the slowest of the 4 physical mediums) you improve performance. By then enabling more data to be stored in the appropriately tuned MySQL Memory buffers, you get a further increase in performance.

For more information on this point, you can contact me at http://ronaldbradford.com/contact

Re: 20 tips for MySQL db architects

#10

Post by tialys » Mon, Oct 20, 2008, 5:45 PM UTC

ronaldbradford wrote: post #7

tialys wrote: post #4

This seems like it could be really handy if someone could perhaps narrate along with it and help me understand what all of his talking points are about.

A video of the presentation can be found at http://technocation.org/node/533/play

Excellent! Thank you.