I found Dennis the Menace, he now has a job as system administrator for a hosting company. Scenario: client has a problem with a server becoming unavailable (cause unknown) and has it restarted. MySQL had some page corruption in the InnoDB tablespace. The hosting provider, being really helpful, goes in as root and first deletes [...]
Filed under: Good practice / Bad practice by arjen on Monday, October 31, 2011 | Social tagging: destruction > helpful > hosting > InnoDB > logfile > mysql > recovery > sysadmin > tablespace
21 Comments »
I’ve done a minor update to the hdlatency tool (get it from Launchpad), it now has a –quick option to have it only do its tests with 16KB blocks rather than a whole range of sizes. This is much quicker, and 16KB is the InnoDB page size so it’s the most relevant for MySQL/MariaDB deployments. [...]
Filed under: Software and tools by arjen on Thursday, June 16, 2011 | Social tagging: hdlatency > InnoDB > iscsi > latency > mariadb > mysql > raid > SAN
2 Comments »
This blag was originally posted at http://cafuego.net/2010/05/26/fast-paging-real-world Some time ago I attended the “Optimisation by Design” course from Open Query¹. In it, Arjen teaches how writing better queries and schemas can make your database access much faster (and more reliable). One such way of optimising things is by adding appropriate query hints or flags. These hints [...]
Filed under: Uncategorized by cafuego on Monday, May 31, 2010 | Social tagging: COUNT > drupal > InnoDB > mysql > SQL_CALC_FOUND_ROWS
6 Comments »
So this is about a SELECT COUNT(*) FROM tblname without a WHERE clause. MyISAM has an optimisation for that since it maintains a rowcount for each table. InnoDB and PBXT can’t do that (at least not easily) because of their multi-versioned nature… different transactions may see a different number of rows for the table table! [...]
Filed under: Good practice / Bad practice by arjen on Thursday, May 27, 2010 | Social tagging: COUNT > index scan > InnoDB > mariadb > MyISAM > mysql > pbxt > reporting
4 Comments »
With Paul McCullagh’s PBXT storage engine getting integrated into MariaDB 5.1, it’s never been easier to it out. So we have, on a slave off one of our own production systems which gets lots of inserts from our Zabbix monitoring system. That’s possibly an ideal usage profile, since PBXT is a log based engine (simplistically [...]
Filed under: Software and tools by arjen on Thursday, May 27, 2010 | Social tagging: InnoDB > mariadb > mysql > pbxt > storage engine > XA
1 Comment »
Ref: Google: Computer memory flakier than expected (CNET DeepTech, Stephen Shankland) Summary: According to tests at Google, it appears that today’s RAM modules have several thousand errors a year, which would be correctable if it weren’t for the fact that most of us aren’t using ECC RAM. Previous research, such as some data from a [...]
Filed under: Uncategorized by arjen on Thursday, October 8, 2009 | Social tagging: corruption > InnoDB > mysql > Open Query > RAM
No Comments »
rsnapshot is a filesystem snapshot utility for making backups of local and remote systems, based on rsync. Rather than just doing a complete copy every time, it uses hardlinks to create incrementals (which are from a local perspective a full backup also). You can specify how long to keep old backups, and all the other [...]
Filed under: Software and tools by arjen on Thursday, September 17, 2009 | Social tagging: backup > InnoDB > mysql > open query > recovery > restore > rsnapshot > rsync > xtrabackup
3 Comments »
When you write your create table statements, always make sure that you make them non-ambiguous. That way even though other servers might have different configurations, you make sure your table will be created in the same way. Imagine for instance you are developing an application on a development server, nicely storing all the scripts you [...]
Filed under: Good practice / Bad practice by Walter Heck on Wednesday, June 24, 2009 | Social tagging: CREATE TABLE > InnoDB > mysql > NO_ENGINE_SUBSTITUTION > sql_mode
2 Comments »
If you use innodb_file_per_table = 1 and innodb_open_files = X (whatever amount is suitable for your server) there’s no way internal to MySQL for finding out how many IBD files InnoDB actually has open. Neither SHOW GLOBAL STATUS LIKE ‘innodb%’ nor SHOW ENGINE INNODB STATUS provide this information. Many sites do have a growing number of tables, [...]
Filed under: Uncategorized by arjen on Tuesday, June 16, 2009 | Social tagging: InnoDB > innodb-file-per-table > innodb-open-files > innodb_file_per_table > innodb_open_files > mysql > open files > open-files-limit > open_files_limit > SHOW ENGINE INNODB STATUS > SHOW GLOBAL STATUS
No Comments »
Keep it. Make sure it gets correctly positioned in the coming months. It appears that with the Oracle acquisition, the reason-to-exist for Falcon is regarded as gone (a non-Oracle-owned InnoDB replacement), previously seen as a strategic imperative – much delayed though. But look, each engine has unique architectural aspects and thus a niche where it [...]
Filed under: Uncategorized by arjen on Thursday, May 14, 2009 | Social tagging: falcon > InnoDB > mysql > Open Query > oracle
3 Comments »