June 20, 2013

Post: Benchmarking Percona Server TokuDB vs InnoDB

table_open_cache = 2048 max_allowed_packet = 16M binlog_cache_size = 16M max_heap_tablemysql/mysql.sock user=root skip-grant-tables TokuDB-related options are all defaults, as I understand from documentation TokuDB comes with good settings

Post: Is Synchronous Replication right for your app?

to get to disk. This has no effect on standard MySQL replication from this instance, since MySQL replication is asynchronous. What about semi-sync MySQLIn Example 2, above, how above moving the ‘joined’ column to the users_groups table so we don’t need to

Post: What to tune in MySQL Server after installation

in MySQL Server straight after installation, assuming it was installed with default settings. I’m surprised how many people fail to provide any reasonable answer to… this to happen so frequently and it is typically best to size your cache so it is large enough to keep most of your tables open

Post: MySQL opening .frm even when table is in table definition cache

MySQL with 100 tables and the table_definition_cache set to 1000. My understanding of this is that MySQL won’t revert to opening the FRM files to read the table… of how the Storage Engine API is called. But back to what the above strace shows. In MySQL 5.5 you can find in sql…

Post: table_cache negative scalability

… me was to see if the problem was fixed in MySQL 5.1 – in this version table_cache was significantly redone and split in table_open_cache and table_definition_cache and… its own cache of file descriptors (set by innodb_open_files) As the time allows I should test if Heikki knows how to implement LRU…

Post: How innodb_open_files affects performance

in terms of optimizations in this space. To keep test alligned to my previous experiments I was running with table_open_cache=64 and tried innodb_open_files=64 and 16384. Reading 100.000 tables first time after MySQL

Post: SHOW OPEN TABLES - what is in your table cache

to examine what tables do you have open right now: mysql> show open tables from test; +———-+——-+——–+————-+ | Database | Table | In_use | Name_locked | +———-+——-+——–+————-+ | test | a | 3 | 0 | +———-+——-+——–+————-+ 1 row in set

Post: Shard-Query EC2 images available

to settable-definition-cache=16384 table-open-cache=128 thread-cache-size=32 thread-stack=256K tmp-table-size=64M transaction-isolation=READ-COMMITTED user=mysql wait-timeout=86400 To

Post: Should we give a MySQL Query Cache a second chance ?

to the core of original implementation which appeared in MySQL 4.0 Query Cache was designed totable invalidation ? It is tricky but I believe it can be done for rather large set of applications. Many applications in MySQL