[Khác] Wordpress High Load

[Chicken Run]

Tình hình là tớ vừa bị suspend trên SiteGround vì tội Highload. Tớ mày mò mãi mà vẫn chưa biết nguyên nhân tại sao, nên post lên đây cho anh em xem, giải quyết hộ tớ với

Đây là nguyên văn SiteGround gửi

Dear Dung,

With this notification we would like to inform you that your account sozzin.net consumes a very high percentage of the server resources and thus affects the performance of the whole shared server.

In order to maintain the stability of the server, we had to temporarily limit the shared server resources your account can use. Please note that this may result in occasional "Resource temporary unavailable" error messages shown on your website.

We are very much aware of the inconvenience this issue may cause you, so we would like to take a moment and explain the reasons for our actions: as you know, your account is hosted on a shared hosting server and thus sharing the resources of the server with other customers' accounts. Even though our shared servers are well optimized, the nature of the shared server is such that no matter how powerful or how well optimized the machine is, it is possible that one user and even one application consumes most of the server resources and overloads the machine. Thus all other accounts on the server stop responding and become inaccessible.

In order to prevent server overload, the source of the high load has to be isolated so that it cannot affect the overall server performance. This is a standard procedure used by all shared hosting providers.

We have conducted a detailed investigation of the reasons for the high resource consumption and it turned out that your application executes slow queries towards its database, which eventually hogs the server. The server tries to execute your slow queries while putting other processes in the queue until some memory is freed. While they are waiting however, they stack up and cause further problems.

We believe you are not causing high server load intentionally and we will do our best to assist you so that your site can be fully functional again as soon as possible.

As mentioned before, the problem is caused by slow queries executed towards your application's database. There can be many reasons for slow database queries, but the following 3 are the most common ones:

1. Large database
2. Not well written scripts
3. Large number of internal links that query the database directly.

Here are some of the database queries that are slow and consume a lot of server resources:


Executed 9 min ago for 8 sec on Database --> sozzin_games.
SELECT `ID`, `post_author`, `post_date`, `post_date_gmt`, `post_status`, `post_name`, `post_modified`, `post_modified_gmt`, `post_parent`, `post_type` FROM `sg_posts` WHERE ( (post_status = 'publish' AND (post_type = 'post' OR post_type = '')) OR (post_status = 'publish' AND post_type = 'page') ) AND post_password='' ORDER BY post_modified DESC
Executed 4 min ago for 12 sec on Database --> sozzin_games.
SELECT `ID`, `post_author`, `post_date`, `post_date_gmt`, `post_status`, `post_name`, `post_modified`, `post_modified_gmt`, `post_parent`, `post_type` FROM `sg_posts` WHERE ( (post_status = 'publish' AND (post_type = 'post' OR post_type = '')) OR (post_status = 'publish' AND post_type = 'page') ) AND post_password='' ORDER BY post_modified DESC
Executed 0 min ago for 12 sec on Database --> sozzin_games.
SELECT `ID`, `post_author`, `post_date`, `post_date_gmt`, `post_status`, `post_name`, `post_modified`, `post_modified_gmt`, `post_parent`, `post_type` FROM `sg_posts` WHERE ( (post_status = 'publish' AND (post_type = 'post' OR post_type = '')) OR (post_status = 'publish' AND post_type = 'page') ) AND post_password='' ORDER BY post_modified DESC


Databases found:
sozzin_games 10Mb.

From the queries above we can conclude that your issue is caused by not well written scripts. In order to have the limitations removed, you should optimize your script so that it consumes less server resources.


Having not well written scripts is a quite complex problem. It may be caused by an additionally installed extension/module that is not working properly, or it may be in the application itself.

If the reason is in an extension/module, the easiest solution would be to disable/remove it. This can usually be done from the application's admin area.

If the problem is in the application itself, solving it may take much more time and effort and will probably require advanced programming skills. In such cases it would be best to contact the application's developers and ask for further assistance. They should be able to examine the issue and offer a suitable solution for it.


There are some general things you can do to optimize your site (such as enable cache). More information on how to optimize your site can be found in our Website Performance Tutorial (http://www.siteground.com/tutorials/...ance/index.htm).

If optimizing the application is not a suitable option for you, we can offer you one of our dedicated solutions (http://www.siteground.com/dedicated_solutions.htm) as an alternative. There all of the system's resources will be dedicated to your account and using a more resource-demanding application will not be a problem.

SiteGround is experienced in providing dedicated hosting solutions and we are happy to inform you that as an existing and loyal SiteGround customer, we will offer you a beneficial upgrade package including:

-No set up fees
-Free website content transfer from the shared server to the dedicated machine
-No website downtime during the upgrade

The upgrade process is simple and straightforward and you can order your dedicated solution upgrade immediately. To do that, please log in your SiteGround User Area -> Order section-> Upgrade to Dedicated Solution option.

If the problem with your application is not resolved in 7 days, we will be forced to take further actions in order to ensure the stability of the shared server.

Thank you in advance for your understanding and cooperation!

Sincerely,
Ilian Ionev,
SiteGround System Administrator
SiteGround.com

Các Mod tớ đã dùng

all-in-one-seo-pack
google-sitemap-generator
profile-pic
search-permalink
wparcade-plugin
wp-pagenavi
wp-postviews
wp-postratings

[AkuVn]

Sử dụng 8 plugin cơ à
Cũng ko phải nhiều nhỉ nhưng có thể đưa link cho các bác pro xem mới biết!

[Hutek]

Cài thêm wp super cache thử xem

[minhmeo.info]

Bỏ đống này đi bạn, tác dụng thì ít mà ảnh hưởng thì nhiều
profile-pic
search-permalink
wparcade-plugin
wp-postviews
wp-postratings

[mrlynx]

all-in-one-seo-pack
google-sitemap-generator
profile-pic
bỏ hết dùng mấy cái trên thôi

[Chicken Run]

Tớ cài WP Super Cache vào thì Google toàn báo Unreadable

[blogtinhoc]

Đây này :

1. Large database
2. Not well written scripts
3. Large number of internal links that query the database directly.

Theo như trên bạn quote lại thì nếu với dung lượng datbase quá lớn, bạn nên mua hót riêng mà dùng cho tiện, các hosting bây giờ cũng không mắc lắmd9e63 sở hữu mà bạn

[rilwis]

Blog của bạn thường có bao nhiêu người online? Nếu con số online khoảng từ 100 trở lên thì vấn đề high load thực sự là đau đầu. Mình đã dính 1 lần như thế, bị nhà cung cấp host suspend vài lần.

Các biện pháp áp dụng với tình trạng này mình dùng gồm:

- cài plugin WP Super Cache. Nếu cái này ko ổn thì phải dùng 1 plugin cache khác, W3 Total Cache chẳng hạn. Cái này thuộc loại ko thể thiếu, nếu ko có cache thì trừ phi bạn có server riêng, có tối ưu các lớp cache ở server, còn ko thì đừng mong chạy trên shared host với no-high load.

- toàn bộ các vị trí có thể chuyển sang html thay vì php được thì nên chuyển. Cái này thường bao gồm: header, footer, sidebar. Nói chung cái gì trên site mà tĩnh, ko thay đổi (VD list các categories) thì thay hết mấy hàm php của WP bằng code html tương ứng.

- cái thứ 3 là tìm cách tích hợp mấy cái plugin trên vào theme để tận dụng những gì cần thiết thôi, loại bỏ những gì ko cần thiết. VD mình đã tích hợp 2 plugin WP Pagenavi và WP Views vào theme.

- tiếp nữa là tìm cách off-load hình ảnh ra khỏi host, càng nhiều càng tốt

Tất nhiên cái quan trọng là chỉ giữ lại những plugin cần thiết, cái gì ko thực sự cần thì bỏ đi, hoặc chịu khó đọc code của nó để lấy những gì cần lấy, còn lại bỏ tất.

Để test 1 cách cẩn thận thì thử thế này: sau khi làm các bước trên, tắt sạch các plugin, để lại cái cache thôi. Lúc đó coi như blog của bạn ở dạng minimized rồi, nếu còn high load nữa thì chỉ có nước đổi host thôi.

Mình đã thử qua JustHost và BlueHost. JustHost ko chịu nổi high load của mình, còn BlueHost thì ok, hiện giờ vẫn đang dùng, mặc dù ko hoàn toàn chịu được, nhưng ko đến nỗi bị suspend.