+ All Categories
Home > Technology > Drizzle Talk

Drizzle Talk

Date post: 29-Jun-2015
Category:
Upload: brian-aker
View: 3,178 times
Download: 0 times
Share this document with a friend
Description:
Drizzle talk for MySQL Developer's Meeting.
Popular Tags:
36
Introduction to Drizzle (it is a type of rain)
Transcript
Page 1: Drizzle Talk

Introduction to Drizzle(it is a type of rain)

Page 2: Drizzle Talk

Master Plan

Page 3: Drizzle Talk

Rethink Everything

Page 4: Drizzle Talk

Do not assume everything was bad.

Page 5: Drizzle Talk

Do Not Live in the Past

Page 6: Drizzle Talk

Multi-Core

• No new locks

• Remove old locks

• Think today:

• Burn memory (copy on write)

• Messages scales.

Page 7: Drizzle Talk

MySQL Market is now just entering 16 Core.

Page 8: Drizzle Talk

Do not play catchup.Leap forward.

Page 9: Drizzle Talk

Leverage Sun

Page 10: Drizzle Talk

Library of Congress is just 26 Terabytes.

Page 11: Drizzle Talk

The world is 64bit, and there is a lot of RAM.

(SSD will be common in two years.)

Page 12: Drizzle Talk

MicroKernel

• Move code to the Edge

• No new features in core

• To add interfaces you have to remove == amount of code

Page 13: Drizzle Talk

We have no...

• Stored Procedures

• Views

• Triggers

• No Query Cache

Page 14: Drizzle Talk

We may though...

Page 15: Drizzle Talk

SP’s through Real Languages

Page 16: Drizzle Talk

Views are useful, but not when materialized

Page 17: Drizzle Talk

Triggers no, but maybe Callbacks...

Page 18: Drizzle Talk

Prepared Statements are out.

(no one uses them, they blow up the server)

Page 19: Drizzle Talk

What we are doing...

• No required authentication (think http)

• Round Trip Serialized SQL

• Make SQL Injection harder

Page 20: Drizzle Talk

Innodb is our Default Engine

(If Maria or PBXT turn out to be faster, we will switch. Transactional/Performance matter.)

Page 21: Drizzle Talk

Dump ACL

• We authenticate in clouds.

• KISS

• PAM (Pluggable Authentication Modules)

• No cost authentication

Page 22: Drizzle Talk

Authorization is coming...

Page 23: Drizzle Talk

Do people really sort blobs?

Page 24: Drizzle Talk

Field Types• Less primitives

• We just now have “blob”

• Weakly Typed.

• 3 byte int? (See Slashdot Comment Problem)

• Think UUID/IPV4(6)/SERIAL...

• ENUM tosses an error if a wrong value is inserted.

Page 25: Drizzle Talk

Интернет является UTF-8.

は、 Web UTF - 8です。

The Web is UTF-8.

Page 26: Drizzle Talk

UTF-8

• Protocol is UTF-8.

• We store in UTF-8.

• (default collation is still up for grabs)

Page 27: Drizzle Talk

Recycle

Page 28: Drizzle Talk

In with the New

• C99 (types for C++ code)

• Posix

• Package-lib

• STL is in.

Page 29: Drizzle Talk

TABLE != Table(we are going from C+ to C++)

Page 30: Drizzle Talk

Reuse many eyeballs

• PCRE today (not REGEX)

• No “shipped” libraries

• Maybe ICU? libatomic-ops? Intel Building Blocks? talloc()? glib()?

• Proto-buffers.

Page 31: Drizzle Talk

How big is it?6.0.5-alpha: 1,128,112

5.1.25-rc: 1,009,108

5.0.51b: 999,382

Drizzle: 315,560

generated using David A. Wheeler's 'SLOCCount'.

Page 32: Drizzle Talk

LaunchPad

• Forking is good.

• No emailed patches.

• Anyone can create an account.

• Neutral ground (this has turned out to be important).

• Short URLs (and yes this matters)

Page 33: Drizzle Talk

Open Source• “Captains” handle trees, karma gets you in

• Those who commit are Janitors.

• Those who only work on their own code are not Captains.

• Changes are sent to mailing list. Fuzzy ++ system used (negatives are weighed more heavily)

Page 34: Drizzle Talk

Code Drives Decisions

Page 35: Drizzle Talk

Requirement for Release

• All Incompatible Changes are completed. (and more require upgrades to version)

• All tests work.

• New code additions are fine (think Linux Kernel)

Page 36: Drizzle Talk

So how do I get involved?

• http://launchpad.net/drizzle

• bzr branch lp:drizzle

• http://launchpad.net/drizzle-discuss

• (mailing list)

• Freenode #drizzle


Recommended