June 20, 2013

Post: New SpecJAppServer results at MySQL and Sun.

…/ innodb_checksums = 0 innodb_doublewrite = 0 innodb_buffer_pool_size = 5000m innodb_additional_mem_pool_size = 20M innodb_log_file_size = 1600M innodb_log_buffer_size = 16M innodb_flush_log_at_trx_commit = 1 innodb_lock_wait_timeout = 300 innodb_thread_concurrency = 0 innodb_sync…

Post: Impact of logging on MySQL’s performance

…; logging every query; MySQL was run with default settings except following: [mysqld] user=root max_connections=3000 innodb_log_file_size=128M innodb_flush_log_at_trx_commit=1 innodb_file_per_table table_cache=2000 Depending on workload different InnoDB buffer was used. In CPU-bound case innodb

Post: Tuning InnoDB Concurrency Tickets

…:autoextend innodb_file_per_table=1 innodb_flush_log_at_trx_commit = 1 innodb_log_buffer_size = 8M innodb_log_files_in_group=2 innodb_log_file_size=1900M innodb_thread_concurrency=16 innodb_flush_method = O_DIRECT innodb_write_io_threads=8 innodb

Post: XtraDB benchmarks - 1.5X gain in IO-bound load

… = 4 innodb_thread_concurrency = 16 innodb_flush_log_at_trx_commit = 1 innodb_log_buffer_size = 8M innodb_log_file_size = 256M innodb_log_files_in_group = 3 innodb_max_dirty_pages_pct = 90 innodb_flush_method=O_DIRECT innodb_file…

Post: Maximal write througput in MySQL

trx_commit=0 : innodb_flush_log_at_trx_commit = 0 and no binary logs trx_commit=1 : innodb_flush_log_at_trx_commit = 1 and no binary logs trx_commit=0 & binlog : innodb_flush_log_at_trx_commit = 0 and binary logs trx_commit=1 & binlog : innodb_flush_log_at_trx_commit = 1 and binary logs trx_commit=1

Post: SHOW INNODB STATUS walk through

… LATEST DETECTED DEADLOCK ———————— 060717 4:16:48 *** (1) TRANSACTION: TRANSACTION 0 42313619, ACTIVE 49 …log file requires. Note depending on your innodb_flush_log_at_trx_commit value your log writes may be more or less expensive. If innodb_flush_logs_at_trx_commit=2 log

Post: Tuning for heavy writing workloads

… above graphs): innodb_flush_log_at_trx_commit = 2 innodb_doublewrite = true top-right: innodb_flush_log_at_trx_commit = 1 innodb_doublewrite = true bottom-left: innodb_flush_log_at_trx_commit = 2 innodb_doublewrite = false bottom-right: innodb_flush_log_at_trx_commit = 1 innodb_doublewrite = false…

Post: SSD, XFS, LVM, fsync, write cache, barrier and lost transactions

…=8M innodb_log_files_in_group=2 innodb_log_file_size=256M innodb_thread_concurrency=0 innodb_flush_log_at_trx_commit=1 innodb_flush_method = O_DIRECT Actually most interesting one are innodb_flush_log_at_trx_commit=1 and innodb_flush_method = O_DIRECT (I tried also default innodb_flush

Post: Heikki Tuuri Innodb answers - Part I

… in MySQL 5.1 Q15: How frequently does Innodb fuzzy checkpointing is activated HT: InnoDB flushes about 128 dirty pages per flush. That means that… way to get good performance is to set innodb_flush_log_at_trx_commit=2, that is, to flush the log to the disk only once per second…

Comment: Product to try: MySQL/MariaDB-Galera 0.8

… performs with innodb_flush_log_at_trx_commit=1. And RAID with BBU is must have for high performance setups, so it rules out problems with innodb_flush_log_at_trx_commit=1. I still want to have innodb_doublewrite=1 even in cluster setup, to be able…