Planet MySQL Planet MySQL: Meta Deutsch Español Français Italiano 日本語 Русский Português 中文
10 Newer Entries Showing entries 41 to 50 of 34742 10 Older Entries
InnoDB vs TokuDB in LinkBench benchmark
+0 Vote Up -0Vote Down

Previously I tested Tokutek’s Fractal Trees (TokuMX & TokuMXse) as MongoDB storage engines – today let’s look into the MySQL area.

I am going to use modified LinkBench in a heavy IO-load.

I compared InnoDB without compression, InnoDB with 8k compression, TokuDB with quicklz compression.
Uncompressed datasize is 115GiB, and cachesize is 12GiB for InnoDB and 8GiB + …

  [Read more...]
How to configure Tcpdump system
+0 Vote Up -0Vote Down

MySQL Tcpdump system : use percona-toolkit to analyze network packages

We can identify problem SQLs with high execution frequency.

With DBMON system and AWR system we can find problem SQLs in a special time (high frequency, occurs over a period of time)

View this PDF:

http://www.vmcd.org/docs/MySQL_TCPDUMP.pdf

Replication in real-time from Oracle and MySQL into data warehouses and analytics
+0 Vote Up -0Vote Down

Practical tips and a live demo of how to get your data warehouse loading projects off the ground quickly and efficiently when replicating from MySQL and Oracle into Amazon Redshift, HP Vertica and Hadoop.

Webinar-on-demand. Recorded 07/23/15.

The Q&A: Creating best-in-class backup solutions for your MySQL environment
+0 Vote Up -0Vote Down

Thank you for attending my July 15 webinar, “Creating Best in Class Backup solutions for your MySQL environment.” Due to the amount of content we discussed and some minor technical difficulties faced near the end of webinar we have decided to cover the final two slides of the presentation along with the questions asked by attendees during the webinar via this blog post.

The …

  [Read more...]
Comment on innodb_fast_checksum=1 and upgrading to MySQL 5.6 by MySQL upgrade 5.6 with innodb_fast_checksum=1 | InsideMySQL
+0 Vote Up -0Vote Down

[…] = CRC32. This is because innodb_checksum_algorithm = INNODB is the default setting. See this post for a sample […]

Altering tablespace of table – new in MySQL 5.7
+0 Vote Up -0Vote Down

Dear community, maybe you have already tested, there are new added features in MySQL 5.7. See previous post -> About 5.7.7-rc BUGs

“General Tablespace” feature -> From now you can place tables to separate tablespaces. Prior, on our hands there were only “System TableSpace” and “InnoDB file per table” options. Today’s topic is altering table to use this “General Tablespace”.

Our sample table structure:

mysql> show create table t1;

    | Table | Create Table …
  [Read more...]
MySQL QA Episode 8: Reducing Testcases for Engineers: tuning reducer.sh
+0 Vote Up -0Vote Down

Welcome to MySQL QA Episode 8: Reducing Testcases for Engineers: tuning reducer.sh

  1. Advanced configurable variables & their default/vanilla reducer.sh settings
    1. FORCE_SKIPV
    2. FORCE_SPORADIC
    3. TIMEOUT_COMMAND & TIMEOUT_CHECK
    4. MULTI_THREADS
    5. MULTI_THREADS_INCREASE
    6. QUERYTIMEOUT
    7. STAGE1_LINES
    8. SKIPSTAGE
    9. FORCE_KILL
  2. Some examples
    1. FORCE_SKIPV/FORCE_SPORADIC
  [Read more...]
Comment on innodb_fast_checksum=1 and upgrading to MySQL 5.6 by MySQL upgrade 5.6 with innodb_fast_checksum=1 | DBA Dojo
+0 Vote Up -0Vote Down

[…] ← innodb_fast_checksum=1 and upgrading to MySQL 5.6 […]

MySQL upgrade 5.6 with innodb_fast_checksum=1
+0 Vote Up -0Vote Down

Summary:

My checklist for performing an in-place MySQL upgrade to 5.6.

Details:

In my previous post, I discussed the problem I had when doing an in-place MySQL upgrade from 5.5 to 5.6 when the database had been running with innodb_fast_checksum=1.

The solution was to use the MySQL 5.7 version of the tool innochecksum. Using this tool on a shutdown database, you can force the checksums on the innodb datafiles to be rewritten into either INNODB or CRC32 format.

Once the MySQL 5.6 upgrade is done, the 5.6 version of mysqld will be able to read the datafiles correctly and not fail …

  [Read more...]
SELinux and the MySQL init script
+0 Vote Up -0Vote Down

I recently worked with a customer who had a weird issue: when their MySQL server was started (Percona Server 5.5), if they try to run service mysql start a second time, the init script was not able to detect that an instance was already running. As a result, it tried to start a second instance with the same settings as the first one. Of course this fails and this creates a mess. What was the issue? A missing rule in SELinux. At least it looks like

Summary

If SELinux is set to enforcing and if you are using Percona Server on CentOS/RHEL 6 (other versions could be affected), service mysql start doesn’t work properly …

  [Read more...]
10 Newer Entries Showing entries 41 to 50 of 34742 10 Older Entries

Planet MySQL © 1995, 2015, Oracle Corporation and/or its affiliates   Legal Policies | Your Privacy Rights | Terms of Use

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.