MySQL on Windows or GNU/Linux

linuxMySQLwindows-server

I've just read this article:
http://dev.mysql.com/tech-resources/articles/move_from_microsoft_SQL_Server.html

There it says that MySQL on Windows is a good choice. (or is what I've understood)

In the article I don't understand if he says that MySQL on Windows is better than on Linux, or just that MySQL on Windows is good enough as Linux.

Now my doubt is:
if I can choose a server dedicated to MySQL and I have to choose between Windows Server 2012 and a free GNU/Linux server distro, which one would have better performances?

May you guys help me understand this?

Best Answer

There are advantages of using Linux as you base for mysql, as others have already covered, but from a performance point of view for many applications you will not see the difference particularly.

While Linux would be my default recommendation too make sure you consider your experience (and that of the people you can immediately call upon if something goes wrong). If you are familiar with Windows but have little sysadmin experience with Linux, go with Windows. Having the knowledge to fix certain things when they go wrong may prove much more important than a performance gain while things are going right, and if got know Windows like the back of your hand you may be able to tune it to the point where it performs better than a similar Linux install that you might produce. Likewise if you have a preference for or more experience with Linux go with that for the same reasons.

Related Solutions

Mysql – Why does MySQL say I’m out of memory

Given this is a Windows installation, @DTest still provided the initial proper direction.

Apply the following formula:

Most people use this:

Maximum MySQL Memory Usage = innodb_buffer_pool_size + key_buffer_size + (read_buffer_size + sort_buffer_size) X max_connections

I prefer this:

Maximum MySQL Memory Usage = innodb_buffer_pool_size + key_buffer_size + ((read_buffer_size + read_rnd_buffer_size + sort_buffer_size + join_buffer_size) X max_connections)

These variables are the ones you need to adjust until the formula yields 80% of installed RAM or less.

sort_buffer_size
read_buffer_size
read_rnd_buffer_size
join_buffer_size
max_connections

Mysql – Why using innodb_file_per_table

I don't think it's a matter of performance but of management.

With separate file per table, you can store different databases in different storage devices for example.

You can deal with the case of very large databases in file systems that can't handle big files (at least postpone the problem until one table reaches the file size limit).

You don't have uncontrolled tablespace growth. If you have some big tables that you drop, the ibdata file stays small.

One aspect that may have some effect on performance is the fragmentation of table data and indexes, which will be limited per table. But that needs testing to be confirmed.

Best Answer

Related Solutions

Mysql – Why does MySQL say I’m out of memory

Mysql – Why using innodb_file_per_table

Related Question