GIGAZINE will be relocated to the new server from Saturday, Sunday, 29th to Sunday 30th

This year'sMoved from January 19th to 20thSince it is a long time since server relocation. "GIGAZINE has been transferred to the new serverIf you can see the article "It is a new server. Until then, we acknowledge that tracking back reception will be paused for convenience of database movement from the time this article was displayed. The new server is as usual.

So, please enjoy how much scary the current server is in the graph of munin below.
In this case, MySQL which existed physically in the same server is made to be another server, so as to reduce the load and increase the processing speed. The recent rise in the load is tremendous, and it will definitely be fatal if it is Web 2.0 net service, perhaps 40 seconds or so until the article is displayed at 12 o'clock in the daytime. It was a state of deafness ... ....

First off from load average. Obviously it's strange recently. Actually, however, it has succeeded in lowering the load from MySQL one week ago. I was surprised that there was a part that could still be tuned. The details are the articles after relocation.


This is the percentage of CPU usage. It seems that there is nothing serious when looking at this, but the 12 o'clock in the daytime has reached 400% dead.


And the content of slow queries that pulls MySQL 's legs. The cause was clearly out of memory. So, I was thinking that it was no longer a level that could be managed anyhow by tuning, but I managed to manage it somehow so recently I got a little bit better.


Also, this time I can relocate the contents of MySQL for the first time without garbled characters .... This is obediently obedient. Last time I ran MySQL from Ver3.x to Ver4.x, so it became a terrible thing ....

Let's meet again with a new server.