<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Parameter on FromDual GmbH</title><link>https://www.fromdual.com/tags/parameter/</link><description>Recent content in Parameter 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>Fri, 19 Mar 2021 16:21:24 +0000</lastBuildDate><atom:link href="https://www.fromdual.com/tags/parameter/index.xml" rel="self" type="application/rss+xml"/><item><title>InnoDB Buffer Pool Instances is too small</title><link>https://www.fromdual.com/blog/innodb-buffer-pool-instances-is-too-small/</link><pubDate>Thu, 16 Jul 2015 20:09:36 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/innodb-buffer-pool-instances-is-too-small/</guid><description>&lt;p&gt;If you are using MariaDB/MySQL 5.5 and newer you should use several InnoDB Buffer Pool Instances for performance reasons.&lt;br&gt;
Some rules to size InnoDB Buffer Pool instances are:&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>Table open cache too small</title><link>https://www.fromdual.com/blog/table-open-cache-too-small/</link><pubDate>Wed, 15 Jul 2015 06:04:36 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/table-open-cache-too-small/</guid><description>&lt;p&gt;The Table Open Cache (&lt;code&gt;table_open_cache&lt;/code&gt; or old name &lt;code&gt;table_cache&lt;/code&gt;) is a cache to store file handles for all threads. The actual value of cache entries can be seen with the global status of open tables (&lt;code&gt;Open_tables&lt;/code&gt;).&lt;br&gt;
Increasing &lt;code&gt;table_open_cache&lt;/code&gt; increases the number of file descriptors (&lt;code&gt;open_files_limit&lt;/code&gt;) that MySQL requires.&lt;br&gt;
You can check whether you need to increase the Table Open Cache by checking &lt;code&gt;Open_tables&lt;/code&gt; and &lt;code&gt;Opened_tables&lt;/code&gt;. If the value of &lt;code&gt;Opened_tables&lt;/code&gt; is large and you do not use &lt;code&gt;FLUSH TABLES&lt;/code&gt; often (which just forces all tables to be closed and reopened), then you should increase the value of the &lt;code&gt;table_open_cache&lt;/code&gt; variable.&lt;/p&gt;</description></item><item><title>InnoDB Flush Method has changed</title><link>https://www.fromdual.com/blog/innodb-flush-method-has-changed/</link><pubDate>Wed, 01 Jul 2015 10:34:36 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/innodb-flush-method-has-changed/</guid><description>&lt;p&gt;The InnoDB Flush Method has changed. This can have an impact on InnoDB write Performance.&lt;/p&gt;</description></item><item><title>MySQL Cluster Local Checkpoint (LCP) and Global Checkpoint (GCP)</title><link>https://www.fromdual.com/blog/mysql-cluster-lcp-gcp/</link><pubDate>Thu, 29 Jul 2010 16:29:48 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/mysql-cluster-lcp-gcp/</guid><description>&lt;p&gt;MySQL Cluster is mainly an in-memory database. Nevertheless it requires a good I/O system for writing various different information to disk.&lt;/p&gt;</description></item><item><title>Some more details about DiskSyncSize</title><link>https://www.fromdual.com/blog/some-more-details-about-disksyncsize/</link><pubDate>Thu, 29 May 2008 14:43:00 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/some-more-details-about-disksyncsize/</guid><description>&lt;p&gt;The parameter &lt;code&gt;DiskSyncSize&lt;/code&gt; is a MySQL Cluster parameter and was added in MySQL 5.1.23.&lt;/p&gt;</description></item></channel></rss>