…: mysql> CREATE TABLE t(id INT AUTO_INCREMENT PRIMARY KEY, c FLOAT) ENGINE=InnoDB; Query OK, 0 rows affected (0.00 sec) mysql> INSERT… TABLE STATUS versus 265 MB index size with the optimization disabled. OPTIMIZE TABLE OPTIMIZE TABLE is mapped to ALTER TABLE … ENGINE… the restore slower; mysqldump –innodb-optimize-keys ignores indexes on AUTO_INCREMENT columns, because they must be indexed, so it is impossible…
Post: Benchmarking single-row insert performance on Amazon EC2
May 16, 2012 By 17 Comments
…Now let’s come to the MySQL configuration. MySQL Configuration I used Percona Server 5…. Other then that, I have also disabled query cache to avoid contention caused…`), KEY `pdc` (`price`,`dateandtime`,`customerid`) ) ENGINE=InnoDB AUTO_INCREMENT=11073789 DEFAULT CHARSET=latin1 /*!50100 PARTITION BY …
Post: MyISAM Scalability and Innodb, Falcon Benchmarks
October 12, 2007 By 10 Comments
…NULL, PRIMARY KEY (`id`), KEY `val` (`val`) ) ENGINE=MyISAM AUTO_INCREMENT=4097 Table t1 contains about 260,000 records, … fixed by changes done in MySQL 4.1 As Monty explained us in MySQL 4.1 the change …_cache is a problem is benchmark run with disabled key_cache (=0). Results for MyISAM with key_…
Comment: MySQL Server Memory Usage
December 20, 2012 By 21 Comments
…=newcrmdb binlog-ignore-db=mysql,test #replicate_do_db=crmdb #replicate_do_db=newcrmdb #auto-increment-increment = 3 #auto-increment-offset = 1 #log-slave-… for compatibility with mysql 3.x # clients (those using the mysqlclient10 compatibility package). #old_passwords=1 # Disabling symbolic-links is…
Post: How to STOP SLAVE on Amazon RDS read replica
December 20, 2012 By 4 Comments
… master> CREATE TABLE percona.test (id int unsigned auto_increment not null primary key); replica> INSERT INTO … that to work, you will also have to disable read_only mode, which you can do … the following to resume replication: replica> CALL mysql.rds_skip_repl_error; master> DROP DATABASE percona;…
Comment: MySQL Installation and upgrade scripts.
May 21, 2007 By 3 Comments
….0.27 – slow, with “check for upgrade” repairs, problems with auto_increment values in the replication binlogs (bug #24432) 5.0.36sp1…, SELinux had to be disabled. At the present time I decided to upgrade to 5.0.36sp1 (MySQL Enperprise) it seems to…
