This is an automated analysis of the
This information should be valid for MySQL 4.1 and 5.0. Since 5.1 is not a final release yet, the numbers should be used as a guide only.
5.1-dd is for tables stored on disk. The ndb_size.pl estimates are experimental and should not be trusted. Notably we don't take into account indexed columns being in DataMemory versus non-indexed on disk.
NOTE the configuration parameters below do not take into account system tables and other requirements.
Parameter | |
---|---|
Usage is in kilobytes. Actual usage will vary as you should set the parameters larger than those listed in the table above.
Parameter | |
---|---|
Column | Type | VARSIZE | Size | Key | |
---|---|---|---|---|---|
We assume that indexes are ORDERED (not created USING HASH). If order is not required, 10 bytes of data memory can be saved per row if the index is created USING HASH
Index | Type | Columns | ||
---|---|---|---|---|
Nr Varsized Attributes | |
---|---|
Row Overhead | |
Varsized Overhead | |
Column DataMemory/Row | |
Index DataMemory/Row | |
Total DataMemory/Row | |
Rows per 32kb page | |
Current number of rows | |
Total DataMemory (kb) |
IndexMemory/Row | |
---|---|
Rows per 8kb page | |
Current number of rows | |
Total IndexMemory (kb) |
This is the output of ndb_size.pl.