… 64 300GB SAS drives, 3 raid controllers and 192GB of RAM. These servers will run a few slave instances each of… handle the write load of all the MySQL instances. The original idea was to configure them with raid-10 + LVM, making sure… ZFS a try. So I trashed the raid-10 arrays, configure JBODs and gave all those drives to ZFS (30 mirrors…
Post: MySQL 5.6 - InnoDB Memcached Plugin as a caching layer
March 29, 2013 By 10 Comments
… or cart object built from several queries) Infrequently changing data (configurations, etc) In pseudo-code, here is the basic approach: data… nutshell, here is how one would start the memcached plugin: mysql> install plugin daemon_memcached soname ‘libmemcached.so’; In an effort… Single core VM 528M RAM Host-Only network 1 Box with http/php, 1 box with memcache or mysql started PHP script…
Comment: Investigating MySQL Replication Latency in Percona XtraDB Cluster
May 17, 2013 By 13 Comments
… we did some R&D on Percona MYSQL server and found that Percona need some configuration setting regarding to memory allocation. So… again performance degradation started and now it is slow again. MySQL load is not going very high. We have also noticed… Admin – 5.3.3 Hardware: Node:2 CPU = Quard Core RAM = 12 GB HDD = 1 TB IP Addresses = 2 Please help…
Post: Online MySQL Configuration Wizard from Percona
December 23, 2011 By 24 Comments
… you configure and manage your MySQL servers. Our online MySQL Configuration Wizard can help you generate a good basic configuration file for a server. This MySQL tuning wizard is our answer to the commonly asked question, “what is a good default configuration file for my server with 16 GB of RAM?” We have a raft of new…
Post: Is there room for more MySQL IO Optimization?
January 3, 2013 By 11 Comments
… — system files, binary log, FRM files, MySQL MyISAM system tables etc. Starting MySQL 5.5 MySQL uses asynchronous IO which should allow it…*7200RPM SATA hard drives in RAID10. It has 8GB of RAM and I’m running Percona Server 5.5.28-29… different read_ahead configuration. Percona Server still allows me to enable Random Read_Ahead which is not available in MySQL 5.5…
Post: Finding an optimal balance of I/O, CPU, and RAM for MySQL
May 16, 2011 By 4 Comments
…, is that as you add CPUs and increase memory size, MySQL doesn’t scale as well as we would like, and… storage — specifically, the Virident tachIOn drive — has more bandwidth than MySQL can fully utilize at present. Therefore, to decrease the price… measuring the different configurations the way Vadim has done. You can read the full details in our Scaling MySQL With Virident Flash…
Post: 128GB or RAM finally got cheap
August 4, 2008 By 14 Comments
… to default configuration to 128GB of memory will cost you just $9600 (list price). I’ve been able to configure on a… RAID and 2 CPUs (just as we usually configure PowerEdge 2950) with 128GB of RAM for about $16000. This means talking to… and 128GB of memory becomes commodity – Quite a challenge for MySQL to take 
I have not had a chance to play…
Post: A piece of Sun/MySQL Marketing
February 27, 2008 By 7 Comments
… components. Looking at container configuration – setting up 6 containers on the same box to run different MySQL and Web instances looks highly… we get configuration with 48 hard drives which is of course far from what you would see in even typical MySQL DB… you can get 2*Quad Core Xeon box w 32G RAM and 8 2.5″ hard drives for about 10K from…
Post: MySQL Master-Master replication manager released
April 5, 2007 By 27 Comments
…mode) is popular pattern used by many companies using MySQL for scale out. Most of the companies would …taken over by passive node and depending on monitoring configuration it can happen within few seconds. Such IP … in clusters to upgrade OS or add more RAM to the system. This tool works well for …
Post: Disaster: MySQL 5.5 Flushing
September 18, 2011 By 27 Comments
… typical nowadays. Hardware: HP ProLiant DL380 G6, with 72GB of RAM and RAID10 on 8 disks. I took sysbench multi-tables… rows each. Total database size ~58GB. MySQL version: 5.5.16 Initial benchmark, which InnoDB configured for this hardware innodb_flush_log… changed data. With widely adoption of MySQL 5.5 and servers with big memory configuration I expect we will see this problem…
