May 26, 2012

Post: What MySQL buffer cache hit rate should you target

per second. And at the same time you have some performance critical transactionto look at the number of misses – number of IOs which MySQL needs to do. You better to look at global and local (per

Post: SHOW INNODB STATUS walk through

MySQL thread id 30898, query id 100626 localhost root Updating update iz set pad=’a’ where i=2 *** (1) WAITING FOR THIS LOCK TOtransactions is displayed, while locks rows could be locked by one of previous statements. For complex deadlock investigations you might need to look at the

Post: Reasons for run-away main Innodb Tablespace

where Trending can help, for example MySQL CACTI Templates will have the graphs you need. If you’re lookingper transactionto be accommodated in the database. It is not limited to undo slots. When we’re speaking about Long Transactions the

Post: Introducing tpce-like workload for MySQL

looking into different benchmarks, and one of them is TPCE. Yasufumi made some efforts to make TPCE working with MySQLwhere you can see count of successful TR (TradeResult) transactions, and the summary result in TpsE (transactions per

Post: MySQL extensions for hosting

for the hardware to process from even small tables. Therefore often the resulting database load may not be directly related to thewhere this patch can be very useful. With simple MySQL SHOW command it gives you the basic statistics on thetransactions: 0 Rollback_transactions: 0 mysqlsec) mysql

Post: How to calculate a good InnoDB log file size

for choosing a configuration setting, you should looksec) Notice the log sequence number. That’s the total number of bytes written to the transactionmysql> select (3838334638 – 3836410803) / 1024 / 1024 as MB_per_min; +————+ | MB_per

Post: Fighting MySQL Replication Lag

transactions all updates from the transactions are buffered together and when dumped toto run UPDATE Example: UPDATE posts SET spam=1 WHERE body LIKE “%cheap rolex%”; This query will perform full table scan in MySQL

Post: Heikki Tuuri answers to Innodb questions, Part II

transactions per second, then you write 1000 times per second! A smart wear leveling should be able to cope with writes to thethe number varied more, depending on the availability of RAM? On a dedicated server for Mysql you will still need some memory for the OS and the

Post: The perils of InnoDB with Debian and startup scripts

for days (or longer). In the meanwhile, it’ll interfere with everything else going on. Look what happens: mysqlfor mutexes, and they are all waiting for thread 1158064464 which has reserved it. If you hunt through the TRANSACTIONS section, you can see the

Post: How much memory Innodb locks really take ?

sec) mysql> select count(*) from sample where j like “5%” lock in share mode; +———-+ | count(*) | +———-+ | 102216 | +———-+ 1 row in set (4.44 sec) Looking