O'Reilly Open Source Convention
Books Safari Bookshelf Conferences O'Reilly Network

Arrow Home
Arrow Registration
Arrow Speakers
Arrow Keynotes
Arrow Tutorials
Arrow Sessions
Arrow At-a-Glance
Arrow Wiki
Arrow BOFs
Arrow Events
Arrow Exhibitors
Arrow Sponsors
Arrow Hotel/Travel
Arrow Venue Map
Arrow See & Do
Arrow Tips for
Arrow Press
Arrow Mail List



Using MySQL for Binary Storage
Mike Kruckenberg, Principal Software Engineer, OpenAir

Track: MySQL
Date: Wednesday, July 28
Time: 1:45pm - 2:30pm
Location: Salon C


Four years ago the Tufts University Sciences Knowledgebase (TUSK) moved it's collection of images from a filesystem into a MySQL database. TUSK, a content management system, has since grown to include a half million images. This presentation digs into the details of using MySQL for storing binary data and serving that data over the Web.

Reasons For and Against MySQL Binary Storage
Passionate debate continues over whether to store binary data as BLOBs in MySQL or to keep it in files on the filesystem. There are good arguments for both sides, which must be weighed when choosing a method of storage.

How-To: Store and Deliver Binary Data
Focus on details in designing the data model and programming to serve the images is key to getting the highest performance.

The biggest question at TUSK is: How well does it perform? Measuring the performance of image delivery is critical in determining the viability of storing binary data in MySQL.

Kruckenberg begins with a review of the arguments for and against binary storage in a database, and how the arguments weighed into TUSK’s decision. He’ll then get under the hood and look at the data model and Apache handler used to store and serve the images. The grand finale will be a show of performance statistics to answer the question “How well will it perform?” Kruckenberg ends with a few thoughts on TUSK’s future plans for MySQL binary storage.

Download presentation file

O'Reilly Home | Privacy Policy

© 2004, O'Reilly Media, Inc.