GIGAZINE finally moved to the new server

So, this is the new generation GIGAZINE.NET by the new server group. The fact that this article is visible means that DNS penetration to the new server has been completed. Although it does not have any particular change in appearance, it should not become heavy unless the server physically causes trouble ... ....

That's why the second story behind the last article. Details are as below.
· Disable DNS lookup for MySQL
It was the biggest problem during the test with the new server configuration. Since the router goes down, I do not know what is going on, and I kept worrying about it for a week and ended up dragging the editorial department of GIGAZINE into the depths of fear. In conclusion, because it was using an external DNS server, DNS references occurred every time a connection to MySQL occurred even in the local test environment.

MySQL :: MySQL 4.1 Reference Manual :: 5.5.5 Using MySQL DNS

When a new client connects to mysqld, mysqld creates a new thread to handle the request. In this thread, it is first checked whether the host name is in the host name cache. Otherwise, the host name resolution will be attempted.

Therefore, at the time of initial boot up, the router was overloaded and the router screamed and shouted "Uja" ... .... I do not understand this, I will make my own router.

In order to solve this, add "--skip-name-resolveOr put it in the setting file my.cnf

[Mysqld]
Skip-name-resolve

It is OK if you write the setting and restart MySQL just in case and reflect the setting.

· Enable persistent connection of MySQL
Again MySQL relationship. Since performance does not come out as much as we thought of in a multiple server configuration, we tried replacing the switching hub and tested it, and even changed it to NIC and washed almost all the patterns, but as a result, in MySQL, If you enable the setting, the problem of server-to-server communication is solved instantly.

MySQL :: MySQL Newsletter Using persistent connections with MySQL

MySQL :: MySQL 4.1 Reference Manual :: 5.2.13 Other Optimization Tips

To avoid connection overhead, use a persistent connection to the database.

It was only to change the setting ......


· Reduce unnecessary queries not used
As a result of many such troubles, it turned out not to be in time for the first deadline at the end of March. Immediately after that, on April 1April Fool articlesWas a big hit, and on April 3rdCurry toppings all togetherHits the article, GIGAZINE has crisis unprecedented. In that case the load looks like the following. First time in history, Load Average, so-called load exceeded 500 hit.

I can not see anything any more.


However, when reviewing with reference to the following page, it turned out that the statistical function was not invalidated.

Reduce Queries | Wiki | ExpressionEngine

Open core / core.system.php and comment out $ STAT-> update_stats ();

I changed the setting with reference to the above page on April 8. As soon as the load drops from 500 to 1 .... I heard a voice saying "Does not it make sense to make a new server?", But considering future things, I do not know when and what kind of access tsunami will strike (eg Yahoo cannon, mixi cannon , Etc., etc.), I thought that it would be more secure if the server configuration with some extensibility was still possible, and this time it became server replacement.

What will happen next when changing the server configuration ... ....