If you have binary logging enabled on your MySQL server (i.e. the log-bin parameter is set in the config file), then you may notice a bulk of large files in the MySQL data directory over time. Generally you only need to enable this binary logging if your server is acting as a relication master or if you need the ability to do point in time recovery from your latest backup. » Read more: Purge MySQL Binary Logs periodically
Archive for the ‘Databases’ category
Purge MySQL Binary Logs periodically
March 9th, 2010Cassandra: Structured Key-Value based storage system
December 11th, 2009Cassandra is an open source distributed database management system. It was initially developed by Facebook for storing very large amounts of data. Jeff Hammerbacher, who led the Facebook Data team at the time, has described Cassandra as a BigTable data model running on a Amazon Dynamo-like infrastructure. » Read more: Cassandra: Structured Key-Value based storage system
Tips for Rebuilding MySQL Replication
November 27th, 2009Let’s keep this post smart. It’s intended to help you rebuild a crashed MySQL replication. We assume that bin-log has been enabled at the master side.
Basically what you need to do is to retrival a snapshot of your master database. It covers three types of information, a snapshot of your current mysql database, and master log file name and its running position when this snapshot created. » Read more: Tips for Rebuilding MySQL Replication
13th Workshop on High Performance Transaction Systems
November 25th, 2009The 13th international workshop on HPTS held at October 25-28, 2009, Pacific Grove, CA. It’s all about real systems problems for real systems builders! The papers are listed at its official website. These papers are really really very informative, it’s suggested to have a read!
Every two years, HPTS brings together a lively and opinionated group of participants to discuss and debate the pressing topics that affect today’s systems and their design and implementation. » Read more: 13th Workshop on High Performance Transaction Systems
MPB: Comparison of MyISAM Infobright and MonetDB
October 7th, 2009This post is originally created by Baron Schwartz at MPB (A.k.a. MySQLPerformanceBlog.com) days ago.
What follows is not a realistic benchmark, it’s not scientific, it’s just some quick and dirty tinkering. Baron threw up an Ubuntu 9.04 small server on Amazon. (Because there’s a .deb of MonetDB for it), and created a table with 200 integer columns and loaded it with random numbers between 0 and 10000. He used default tuning, out of the box, for all three databases. » Read more: MPB: Comparison of MyISAM Infobright and MonetDB
PostgreSQL Database Performance Tips
September 11th, 2009What follows for the next few posts is a somewhat edited version of a set of advice I am giving to a Sun team on redesigning a C++ application which was built for MySQL, ported to PostgreSQL, and never performance optimized. It occurred to me that this advice would be generally useful to the community, so here goes. (and yes, I’ll pick up “Four Horsemen” again eventually.) » Read more: PostgreSQL Database Performance Tips
Repair MySQL Replication by SQL_SLAVE_SKIP_COUNTER
September 11th, 2009If you set up MySQL replication, you probably have ever faced this problem. there are invalid MySQL queries which cause the replication not to work anymore. Here I’ll explain how you can repair the replication on MySQL slave without rebuilding the whole repication environment. There are two steps here: » Read more: Repair MySQL Replication by SQL_SLAVE_SKIP_COUNTER
MPB: InnoDB vs MyISAM vs Falcon
September 11th, 2009MySQLPerformanceBlog has issue “Several days ago MySQL AB made new storage engine Falcon available for wide auditory. We cannot miss this event and executed several benchmarks to see how Falcon performs in comparison to InnoDB and MyISAM. » Read more: MPB: InnoDB vs MyISAM vs Falcon
Performance Tuning PostgreSQL
September 8th, 2009PostgreSQL is the most advanced and flexible Open Source SQL database today. With this power and flexibility comes a problem. How do the PostgreSQL developers tune the default configuration for everyone? Unfortunately the answer is they can’t.
The problem is that every database is not only different in its design, but also its requirements. Some systems are used to log mountains of data that is almost never queried. Others have essentially static data that is queried constantly, sometimes feverishly. Most systems however have some, usually unequal, level of reads and writes to the database. Add this little complexity on top of your totally unique table structure, data, and hardware configuration and hopefully you begin to see why tuning can be difficult.
Please check the original version here: Performance Tuning PostgreSQL