<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Optimize on FromDual GmbH</title><link>https://www.fromdual.com/tags/optimize/</link><description>Recent content in Optimize on FromDual GmbH</description><generator>Hugo</generator><language>en-GB</language><managingEditor>oli.sennhauser@fromdual.com (Oli Sennhauser)</managingEditor><webMaster>oli.sennhauser@fromdual.com (Oli Sennhauser)</webMaster><copyright>© FromDual GmbH</copyright><lastBuildDate>Sun, 08 Feb 2026 16:15:00 +0100</lastBuildDate><atom:link href="https://www.fromdual.com/tags/optimize/index.xml" rel="self" type="application/rss+xml"/><item><title>To NULL, or not to NULL, that is the question!</title><link>https://www.fromdual.com/blog/to-null-or-not-to-null-that-is-the-question/</link><pubDate>Fri, 14 Dec 2018 08:33:25 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/to-null-or-not-to-null-that-is-the-question/</guid><description>&lt;p&gt;As we already stated in earlier articles in this blog &lt;br&gt;[&lt;a href="https://www.fromdual.com/using-null-as-default-values" title="Using NULL as default values"&gt;1&lt;/a&gt; and &lt;a href="https://www.fromdual.com/mariadb-indexing-of-null-values" title="MariaDB indexing of NULL values"&gt;2&lt;/a&gt;&lt;br&gt;] it is a good idea to use &lt;code&gt;NULL&lt;/code&gt; values properly in MariaDB and MySQL.&lt;/p&gt;</description></item><item><title>Table definition cache too small</title><link>https://www.fromdual.com/blog/table-definition-cache-too-small/</link><pubDate>Wed, 15 Jul 2015 06:08:36 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/table-definition-cache-too-small/</guid><description>&lt;p&gt;The number of table definitions (&lt;code&gt;SHOW CREATE TABLE&amp;lt;br&amp;gt;G&lt;/code&gt;) that can be stored in the table definition cache (&lt;code&gt;table_definition_cache&lt;/code&gt;). If you have a large number of tables (&lt;br&gt;&amp;gt; 400) in your database instance, you should consider a larger table definition cache to increase your database throughput and decrease your query latency.&lt;br&gt;
The command &lt;code&gt;SELECT COUNT(*) FROM information_schema.tables;&lt;/code&gt; shows you how many tables and thus table definitions you have. The global status &lt;code&gt;Open_table_definitions&lt;/code&gt; is the current amount of open table definitions.&lt;/p&gt;</description></item><item><title>How much space does NULL need?</title><link>https://www.fromdual.com/blog/how-much-space-does-null-need/</link><pubDate>Sun, 08 Feb 2026 16:15:00 +0100</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/how-much-space-does-null-need/</guid><description>&lt;p&gt;The last time I consulted a customer, he came up to me beaming with joy and said that he had taken my advice and changed all the primary key columns from &lt;code&gt;BIGINT&lt;/code&gt; (8 bytes) to &lt;code&gt;INT&lt;/code&gt; (4 bytes) and that had made a big difference! His MySQL 8.4 database is now 750 Gbyte smaller (from 5.5 Tbyte). Nice!&lt;/p&gt;</description></item></channel></rss>