In the last episode (Dec 05), Michael She said:
> I'm planning to run a remote DB across the internet for a web
> application and I would like to minimize retrival times and
> bandwidth.
>
> I have a couple of questions about MyISAM compressed Tables:
>
> 1. Is it slower to retrieve from a compressed table, or actually
> faster since data is packed?
Slightly faster, but the difference is nothing compared to disk seek
times, so you'll never notice it. Also note that compressed tables are
read-only.
> 2. Is there an increase in CPU overhead? Is it significant?
Minimal.
> 3. Is the data sent to the client compressed or decompressed?
Protocol compression is separate from Table compression. To enable
protocol compression, set the CLIENT_COMPRESS flag when connecting to
the server, or add the "compress" keyword to the [client] block of your
my.cnf file.
> As for indicies is it better to create a single index per column, or
> an index for a set of columns. For example, if I go: SELECT * FROM
> SOMETABLE WHERE A = X and B = Y. Is it better to create a X AND Y
> index, or two separate indicies?
For that partucilar query, you need a single index over both columns,
since Mysql will only use one index per table.
--
Dan Nelson
[EMAIL PROTECTED]
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
