Re: data disk tablespaces

On Fri, 2007-07-06 at 17:10 -0500, Brian Moon wrote:
> 1. Is it better to make one tablespace per table that you want to store
> on disk or to have one large tablespace that multiple tables can use?

fewer tablespaces are easier to manage :)

> 2. Is it better to have lots of little data files (20X50MB) or just a
> few big ones (4X256MB)?

probably the few... although IIRC our recommended limit is 16GB per datafile...

> 3. What else do the docs not tell me about data disks?
>
> FWIW, we have an application that stores several TEXT fields. The sucky
> thing is that the fields are usually like 400 bytes. Too big for a
> varchar, but big enough to make a 2k chunk to store blob data. That is
> occupying about 80% of our cluster storage. That data can easily go to
> disk afaik with 5.1 thus freeing up a lot of room for us in our cluster.
> We are running at about 48% capacity in our production cluster and
> still have several applications to port over. We want to be ready for
> 5.1 when it hits ( or frankly before if its our best option for meeting
> our space requirements and we have spent enough time with it ).

5.1-telco has the 2k chunk as a varsized attribute... so saving the space there.

Otherwise, storing these on disk could help a lot.

-- 
Stewart Smith, Senior Software Engineer
MySQL AB, www.mysql.com
Office: +14082136540 Ext: 6616
VoIP: 6616@sip.us.mysql.com
Mobile: +61 4 3 8844 332

Jumpstart your cluster:
http://www.mysql.com/consulting/packaged/cluster.html


application/pgp-signature attachment: This is a digitally signed message part