#msyql

Tuesday - October 13, 2015 at 3:16 PM

I used MAMP. Installation was pretty easy for Apache/nginx with MySQL. But, I felt that it becomes quite heavy for my machine (Macbook Air 2011). Then I moved to XAMPP. Installation was pretty easy as well. But still, quite heavy for my machine. Tried Docker with Kitematic. Having no problem installing MySQL. But since Docker is using virtualization, it felts heavy on my machine. Now, I'm using native MySQL package.

Download MySQL .dmg file from http://dev.mysql.com/downloads/mysql/

Install the downloaded file. A MySQL panel will be shown in System Preference if installation succeed.

To connect with MySQL, open terminal and type :

/usr/local/mysql/bin/mysql -u root -h localhost -p

Most of high scale web applications use MySQL + memcached. Many of them use also NoSQL like TokyoCabinet/Tyrant. In some cases people have dropped MySQL and have shifted to NoSQL. One of the biggest reasons for such a movement is that it is said that NoSQL performs better than MySQL for simple access patterns such as primary key lookups. Most of queries from web applications are simple so this seems like a reasonable decision.   Like many other high scale web sites, we at DeNA had similar issues for years. But we reached a different conclusion. We are using "only MySQL". We still use memcached for front-end caching (i.e. preprocessed HTML, count/summary info), but we do not use memcached for caching rows. We do not use NoSQL, either. Why? Because we could get much better performance from MySQL than from other NoSQL products. In our benchmarks, we could get 750,000+ qps on a commodity MySQL/InnoDB 5.1 server from remote web clients. We also have got excellent performance on production environments.    Maybe you can't believe the numbers, but this is a real story. In this long blog post, I'd like to share our experiences.