June 20, 2013

Post: Percona Server 5.1.69-14.7 now available: A drop in replacement for MySQL

… vulnerability, where an unprivileged MySQL account owner could perform brute-force password guessing attack …for the log reads needlessly, potentially limiting performance on write-intensive workloads. Bug fixed #1171699. … I/O error occurs after an INNODB_CHANGED_PAGES query started returning data …

Post: Percona Server 5.6.11-60.3 first Release Candidate now available

… id=”attachment_13396″ align=”alignright” width=”247″] Percona Server for MySQL version 5.6.11-60.3[/caption] Percona is glad… now allocated calling calloc() directly instead of using InnoDB heap allocation. This may improve write performance for high levels of concurrency. Bug fixed…

Post: Percona Server for MySQL 5.5.31-30.3 now available

write support for directFS filesystem on Fusion-io devices. This feature implementation is considered BETA quality. Percona Server has introduced innodb…the CVE-2012-5627 vulnerability, where an unprivileged MySQL account owner could perform brute-force password guessing attack on other accounts …

Post: ZFS on Linux and MySQL

… will perform the backups.  The write load is not excessive so a single server can easily handle the write load of all the MySQL… but… since it is a copy on write filesystem, the snapshots are free, no performance penalty.  You can easily run a server… many scripts ready for the task.  Snapshots work best with InnoDB, with MyISAM you’ll have to start the snapshot while…

Post: Percona Server for MySQL 5.5.30-30.2 now available

MySQL performance can be found in this blogpost. (Ignacio Nin) This release of Percona Server for MySQL has fixed a number of performance bugs. (Alexey Kopytov) Drop table performance feature has been removed and its controlling variable innodb

Post: Benchmarking Percona Server TokuDB vs InnoDB

InnoDB performance steadily declines from 24000 tps to 18000 tps, but InnoDBinnodb_read_io_threads = 16 innodb_write_io_threads = 4 innodb_io_capacity = 4000 innodb_use_native_aio=0 #not innodb

Post: MySQL and Percona Server in LinkBench benchmark

…-bounds case MySQL performs quite well, though we can see small performance drop in MySQL 5.6. In IO-bound cases MySQL still has performance issues…=128M innodb_max_dirty_pages_pct=80 innodb_file_format=barracuda innodb_file_per_table innodb_read_io_threads = 8 innodb_write_io_threads = 8 innodb_io…

Post: The write cache: Swap insanity tome III

…been something bad for MySQL performance but it is even more important for HA…MySQL process using the numactl utility, drop the file cache and pre-allocate the innodb buffer pool with the innodb… but doing very little physical writes. The writes were cached and the write cache was causing the problem….

Post: More on MySQL transaction descriptors optimization

…= 8 innodb_write_io_threads = 8 innodb_io_capacity = 2000 max_connections=5000 table_open_cache=5000 query_cache_type=OFF performance_schema=… –max-requests=0 –percentile=99 –mysql-user=root –mysql-db=sbtest8t1M –mysql-table-engine=INNODBmysql-socket=/tmp/mysql.sock –oltp-point-selects=1 –…

Post: Percona Server 5.5.30-30.2 rerelease fixes non-restart issue

MySQL performance can be found in this blogpost. (Ignacio Nin) This release of Percona Server for MySQL has fixed a number of performance bugs. (Alexey Kopytov) Drop table performance feature has been removed and its controlling variable innodb