I dont know why my VPS is get out of resources

I have a website on a VPS hosting and is out of resources now, I dont have a so big traffic but I talk to the suport and they show say that for me:

The main reason for the high CPU and memory consumption is the heavy mysql queries that your website is performing due to the high access rate on the site:

nobody 32675 0.0 0.1 9692 2708 ? S 07:37 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1836 0.1 0.1 9272 2332 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1843 0.1 0.1 9640 2660 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1845 0.1 0.1 9392 2448 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1846 0.2 0.1 9576 2628 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
meetwebc 5694 6.5 1.9 86264 29212 ? D 08:03 0:00 | _ /usr/bin/php /home/meetwebc/public_html/modules/inde
nobody 1847 0.2 0.1 9284 2336 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1848 0.2 0.1 9704 2688 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1851 0.1 0.1 9652 2652 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1852 0.1 0.1 9652 2652 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1855 0.1 0.1 9272 2312 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1856 0.1 0.1 9296 2352 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1857 0.1 0.1 9276 2316 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1858 0.2 0.1 9604 2608 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1859 0.1 0.1 9272 2328 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
meetwebc 5739 39.0 1.9 86264 29212 ? D 08:03 0:00 | _ /usr/bin/php /home/meetwebc/public_html/modules/inde
nobody 1864 0.1 0.1 9272 2332 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1865 0.1 0.1 9272 2312 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1866 0.1 0.1 9272 2336 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1867 0.1 0.1 9268 2252 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1868 0.1 0.1 9268 2320 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1869 0.1 0.1 9588 2596 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
meetwebc 5709 9.0 1.9 86264 29208 ? D 08:03 0:00 | _ /usr/bin/php /home/meetwebc/public_html/modules/inde
nobody 1870 0.1 0.1 9604 2584 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1871 0.1 0.1 9328 2368 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1872 0.1 0.1 9276 2268 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1873 0.2 0.1 9640 2644 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1874 0.1 0.1 9268 2324 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
meetwebc 5732 20.0 1.9 86264 29212 ? D 08:03 0:00 | _ /usr/bin/php /home/meetwebc/public_html/modules/inde
nobody 1875 0.2 0.1 9264 2332 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
meetwebc 5673 7.8 0.0 0 0 ? Z 08:03 0:00 | _ [php] <defunct>
nobody 1877 0.1 0.1 9600 2580 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1878 0.1 0.1 9644 2616 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1879 0.1 0.1 9260 2332 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
meetwebc 5731 41.5 2.4 93468 36644 ? R 08:03 0:00 | _ /usr/bin/php /home/meetwebc/public_html/index.php
nobody 1880 0.1 0.1 9288 2328 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1881 0.0 0.1 9276 2332 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
meetwebc 5740 7.0 0.0 0 0 ? Z 08:03 0:00 | _ [php] <defunct>
root 5746 0.0 0.0 3096 972 ? R 08:03 0:00 | _ /opt/suphp/sbin/suphp
nobody 1882 0.1 0.1 9264 2276 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
meetwebc 5748 40.0 1.7 83416 26272 ? R 08:03 0:00 | _ /usr/bin/php /home/meetwebc/public_html/profile.php
nobody 1884 0.1 0.1 9264 2308 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1886 0.1 0.1 9256 2252 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
meetwebc 5715 11.6 1.9 86252 29220 ? D 08:03 0:00 | _ /usr/bin/php /home/meetwebc/public_html/modules/inde
nobody 1887 0.1 0.1 9252 2380 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1888 0.1 0.1 9272 2332 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1889 0.1 0.1 9696 2652 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1890 0.1 0.1 9708 2652 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1893 0.1 0.1 9248 2364 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1894 0.1 0.1 9272 2324 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
meetwebc 5745 11.0 1.3 77432 19948 ? R 08:03 0:00 | _ /usr/bin/php /home/meetwebc/public_html/modules/inde
nobody 1895 0.1 0.1 9264 2304 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1897 0.1 0.1 9672 2612 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1898 0.2 0.1 9648 2704 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1899 0.2 0.1 9580 2576 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1900 0.1 0.1 9592 2572 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
meetwebc 5707 10.3 1.9 86264 29220 ? D 08:03 0:00 | _ /usr/bin/php /home/meetwebc/public_html/modules/inde
nobody 1901 0.1 0.1 9284 2280 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1902 0.1 0.1 9280 2332 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1903 0.1 0.1 9592 2592 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1904 0.1 0.1 9692 2684 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1905 0.1 0.1 9584 2604 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1906 0.1 0.1 9664 2660 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1907 0.1 0.1 9272 2264 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1908 0.2 0.1 9632 2632 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1910 0.1 0.1 9268 2320 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1911 0.1 0.1 9344 2380 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1912 0.1 0.1 9588 2648 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1914 0.1 0.1 9632 2568 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1938 0.1 0.1 9600 2580 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1939 0.1 0.1 9248 2236 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
meetwebc 5741 50.0 2.2 91164 33840 ? R 08:03 0:00 | _ /usr/bin/php /home/meetwebc/public_html/index.php
nobody 1944 0.1 0.1 9268 2248 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 1950 0.1 0.1 9248 2364 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 2002 0.1 0.1 9616 2612 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 2006 0.2 0.1 9588 2568 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 2007 0.1 0.1 9264 2320 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
nobody 2025 0.1 0.1 9640 2640 ? S 08:00 0:00 _ /usr/local/apache/bin/httpd -DSSL
meetwebc 5738 27.0 1.9 86264 29216 ? D 08:03 0:00 | _ /usr/bin/php /home/meetwebc/public_html/modules/inde

As a result of these requests the mysql is consuming about 90% of the CPU of your virtual server:

| 508363 | meetwebc_dolp925 | localhost | meetwebc_dolp925 | Sleep | 1 | | |
| 508366 | meetwebc_dolp925 | localhost | meetwebc_dolp925 | Sleep | 1 | | |
| 508367 | meetwebc_dolp925 | localhost | meetwebc_dolp925 | Sleep | 1 | | |
| 508368 | meetwebc_dolp925 | localhost | meetwebc_dolp925 | Sleep | 0 | | |
| 508369 | meetwebc_dolp925 | localhost | meetwebc_dolp925 | Sleep | 1 | | |
| 508370 | meetwebc_dolp925 | localhost | meetwebc_dolp925 | Sleep | 0 | | |
| 508371 | meetwebc_dolp925 | localhost | meetwebc_dolp925 | Sleep | 0 | | |
| 508372 | meetwebc_dolp925 | localhost | meetwebc_dolp925 | Sleep | 0 | | |
| 508373 | meetwebc_dolp925 | localhost | meetwebc_dolp925 | Sleep | 0 | | |

As a possible solution in this matter you may consider optimizing your website and mysql queries or consider upgrading your VPS to a more powerful one or fully dedicated hosting server. In order to optimize your website you may take the following steps:

1) Reduce the number of records, articles, information blocks and content displayed per page
2) Optimize your database by reducing its size. This can be achieved by removing old posts, truncating cache, logs or other large tables of your database or enabling application cache. 
3) Check your database size and make sure that there are no spam records such as spam user registrations, spam comments or spam posts.

You may also consider upgrading your server to a more powerful virtual one or a fully dedicated hosting server. You may review our VPS and Dedicated server offers.

Does anybody knows a solution for these problem to dont have to upgrade to a dedicated server ? because is too much money for me now and I dont receive nothing for my website yet.

Regards.

Gabriel.

Quote · 4 May 2013

These lines are chopped off and incomplete.

meetwebc 5694 6.5 1.9 86264 29212 ? D 08:03 0:00 | _ /usr/bin/php /home/meetwebc/public_html/modules/inde

So it's not possible for us to know which module would be the problem based on that report.

Anyhow. Dolphin does have certain requirements, and all hosts are not the same. What are the specs on your VPS and how much traffic do you currently get. We may be able to provide you with better hosting solutions.

https://www.deanbassett.com
Quote · 4 May 2013

I think it will be index.php, as i see them in logs many times. Maybe because it is used like a bootstrap. 

meetwebc 5694 6.5 1.9 86264 29212 ? D 08:03 0:00 | _ /usr/bin/php /home/meetwebc/public_html/modules/inde

For the problem (as deano said) we need to know what your vps specs is and how much active user you have on site at any given time. Anyway there are many things to optimize a site and server.

so much to do....
Quote · 4 May 2013

I had a VPS with Constant.com; first time I have actually named them, and had nothing but issues.  Some VPS providers will put way too many accounts on the same box; which then becomes just as bad as shared hosting.  My guess is that you need to either find a better VPS provider or move to a dedicated box.

I would not suggest staying with your present provider due to the recommendations they made to you.  It sounds like they know they over sell their boxes to begin with.

Geeks, making the world a better place
Quote · 4 May 2013

Also have you check your PHP.INI file to make sure you are not restricting the amount of memory.

 

and do you know the handler you have set in PHP?

 

If you are using a cPanel VPS you can swap this easly to somthing like suPHP or DSO etc.

each one has it's good and bad points. 

~~Mike ~~ This Signature is missing something :(
Quote · 4 May 2013

HI.

What hosting VPS plan do you recommend to me to use with my boonex website ?

Quote · 18 May 2013

 

HI.

What hosting VPS plan do you recommend to me to use with my boonex website ?

I can not recommend a VPS but I can warn you to stay clear of Constant.com

Geeks, making the world a better place
Quote · 18 May 2013

try either

http://www.vpsville.ca/cpanel-vps (All the plans on this page come with a cPanel license and CentOS)

 

or

http://www.vpsville.ca/semi-dedicated

the Semi Dedicated dose not come with cPanel installed so you would need to get a license and install this (I have done this and it's simple enough) but have more power as you only share the node with up to 8 other users. you also have a choice of Linux Distro. (I would use CentOS if you want to install cPanel)

 

Both plans come with full root access and easy server management to clear the firewall, re-install OS and power options.

~~Mike ~~ This Signature is missing something :(
Quote · 21 May 2013

You can get a VPS from hostgator if you really want trouble free and good server. They will not oversell their server for sure.

so much to do....
Quote · 21 May 2013
 
 
Below is the legacy version of the Boonex site, maintained for Dolphin.Pro 7.x support.
The new Dolphin solution is powered by UNA Community Management System.