<title>MySQL Cluster size estimate for <TMPL_VARNAME="db"ESCAPE="HTML"></title>
<style type="text/css">
table{border-collapse:collapse}
td,th{border:1pxsolidblack}
</style>
</head>
<body>
<h1>MySQL Cluster analysis for <TMPL_VARNAME="db"escape="html"></h1>
<p>This is an automated analysis of the <TMPL_VARNAME="DSN"escape="html"> database for migration into <ahref="http://www.mysql.com/">MySQL</a> Cluster. No warranty is made to the accuracy of the information.</p>
<p>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.</p>
<p>5.1-dd is for tables stored on disk. The ndb_size.pl estimates are <b>experimental</b> and should not be trusted. Notably we don't take into account indexed columns being in DataMemory versus non-indexed on disk.</p>
<h2>Parameter Settings</h2>
<p><b>NOTE</b> the configuration parameters below do not take into account system tables and other requirements.</p>
<table>
<tr>
<th>Parameter</th>
<TMPL_LOOPNAME=releases>
<th><TMPL_VARNAME=rel></th>
</TMPL_LOOP>
</tr>
<TMPL_LOOPNAME=Parameters>
<tr>
<td><TMPL_VARNAME=name></td>
<TMPL_LOOPNAME=releases>
<td><TMPL_VARNAME=val></td>
</TMPL_LOOP>
</tr>
</TMPL_LOOP>
</table>
<h2>Memory usage because of parameters</h2>
<p>Usage is in kilobytes. Actual usage will vary as you should set the parameters larger than those listed in the table above.</p>
<p>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</p>