Page 2 of 2 FirstFirst 12
Results 26 to 43 of 43

Thread: VPS Load

  1. #26
    load is incredible high on my 3 VPS. THisa is what i seen in TOP on on of my VPS:

    Code:
    top - 08:49:21 up  1:39,  1 user,  load average: 18.55, 19.52, 18.52
    Tasks: 124 total,   5 running, 119 sleeping,   0 stopped,   0 zombie
    Cpu(s): 12.8% us,  0.9% sy,  0.0% ni, 41.2% id, 45.1% wa,  0.0% hi,  0.0% si
    Mem:   8298896k total,  8281680k used,    17216k free,   102844k buffers
    Swap:  8385920k total,  2033576k used,  6352344k free,  2458396k cached
      PID USER      PR  NI %CPU    TIME+  %MEM  VIRT  RES  SHR S COMMAND
    20060 nobody    16   0   47   0:45.49  0.8  144m  63m  15m S /usr/local/apache/bin/httpd -DSSL
    30220 mysql     15   0    2   1:21.79  0.3  173m  26m 3336 S /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/server.an-dns6.com.pid --skip-external-locking --sock
    20098 nobody    16   0    1   0:42.48  0.8  144m  61m  13m S /usr/local/apache/bin/httpd -DSSL
     1662 username  15   0    0   0:04.19  0.4 33140  30m 2040 D spamd child
     7205 root      16   0    0   0:02.36  0.0  2024 1084  788 S top -c
     5775 mailnull  16   0    0   0:00.03  0.0  9168 4032 2696 S /usr/sbin/exim -bd -q60m
        1 root      15   0    0   0:00.11  0.0  1628  604  524 S init [3]
    24199 root      15   0    0   0:00.28  0.0  1532  528  440 S syslogd -m 0
    24420 named     19   0    0   0:17.98  0.1 77248  11m 1912 S /usr/sbin/named -u named
    29866 root      16   0    0   0:00.00  0.0  1456  376  320 S /usr/sbin/courierlogger -pid=/var/spool/authdaemon/pid -facility=mail -start /usr/libexec/courier-authlib/authdaemond
    29867 root      15   0    0   0:00.00  0.0  1804  592  484 S /usr/libexec/courier-authlib/authdaemond
    29894 root      15   0    0   0:00.01  0.0  5764 1784 1360 S cupsd
    29939 root      15   0    0   0:00.00  0.0  1804  360  240 S /usr/libexec/courier-authlib/authdaemond
    29942 root      15   0    0   0:00.00  0.0  1804  360  240 S /usr/libexec/courier-authlib/authdaemond
    29944 root      16   0    0   0:00.00  0.0  1804  356  236 S /usr/libexec/courier-authlib/authdaemond
    29945 root      16   0    0   0:00.00  0.0  1804  360  240 S /usr/libexec/courier-authlib/authdaemond
    29946 root      16   0    0   0:00.00  0.0  1804  360  240 S /usr/libexec/courier-authlib/authdaemond
    29947 root      15   0    0   0:00.00  0.0  1804  356  236 S /usr/libexec/courier-authlib/authdaemond
    29949 root      16   0    0   0:00.00  0.0  1804  360  240 S /usr/libexec/courier-authlib/authdaemond
    29950 root      15   0    0   0:00.00  0.0  1804  360  240 S /usr/libexec/courier-authlib/authdaemond
    29951 root      15   0    0   0:00.00  0.0  1804  360  240 S /usr/libexec/courier-authlib/authdaemond
    29952 root      15   0    0   0:00.00  0.0  1804  360  240 S /usr/libexec/courier-authlib/authdaemond
    30091 root      15   0    0   0:00.00  0.0  4024 1032  740 S /usr/sbin/sshd
    30138 root      18   0    0   0:00.00  0.0  2084  780  652 S xinetd -stayalive -pidfile /var/run/xinetd.pid
    30161 root      18   0    0   0:00.00  0.0  2152 1120  956 S /bin/sh /usr/bin/mysqld_safe --datadir=/var/lib/mysql --pid-file=/var/lib/mysql/server.an-dns6.com.pid
    30588 root      15   0    0   0:00.10  0.0  5672 4092 1216 S chkservd
    30618 root      16   0    0   0:00.00  0.0  1460  380  320 S /usr/sbin/courierlogger -pid=/var/run/imapd.pid -start -name=imapd /usr/lib/courier-imap/libexec/couriertcpd -address=0 -maxprocs=100 -maxperip=50
    30619 root      16   0    0   0:00.00  0.0  1568  516  440 S /usr/lib/courier-imap/libexec/couriertcpd -address=0 -maxprocs=100 -maxperip=50 -nodnslookup -noidentlookup 143 /usr/lib/courier-imap/sbin/imaplog
    30642 root      20   0    0   0:00.00  0.0  1460  312  260 S /usr/sbin/courierlogger -pid=/var/run/imapd-ssl.pid -start -name=imapd-ssl /usr/lib/courier-imap/libexec/couriertcpd -address=0 -maxprocs=100 -max
    30643 root      18   0    0   0:00.00  0.0  1568  488  412 S /usr/lib/courier-imap/libexec/couriertcpd -address=0 -maxprocs=100 -maxperip=50 -nodnslookup -noidentlookup 993 /usr/lib/courier-imap/bin/couriert
    30649 root      15   0    0   0:00.03  0.0  1460  380  320 S /usr/sbin/courierlogger -pid=/var/run/pop3d.pid -start -name=pop3d /usr/lib/courier-imap/libexec/couriertcpd -address=0 -maxprocs=50 -maxperip=50
    30650 root      16   0    0   0:00.04  0.0  1568  516  440 S /usr/lib/courier-imap/libexec/couriertcpd -address=0 -maxprocs=50 -maxperip=50 -nodnslookup -noidentlookup 110 /usr/lib/courier-imap/sbin/pop3logi
    30661 root      18   0    0   0:00.00  0.0  1460  312  260 S /usr/sbin/courierlogger -pid=/var/run/pop3d-ssl.pid -start -name=pop3d-ssl /usr/lib/courier-imap/libexec/couriertcpd -address=0 -maxprocs=50 -maxp
    30663 root      18   0    0   0:00.00  0.0  1568  488  412 S /usr/lib/courier-imap/libexec/couriertcpd -address=0 -maxprocs=50 -maxperip=50 -nodnslookup -noidentlookup 995 /usr/lib/courier-imap/bin/couriertl
    32707 root      16   0    0   0:00.27  0.1  6408 4920 2644 S /etc/authlib/authProg
     1334 root      17   0    0   0:00.21  0.1  6408 4908 2636 S /etc/authlib/authProg
     1390 root      16   0    0   0:00.26  0.1  6408 4920 2644 S /etc/authlib/authProg
     1391 root      17   0    0   0:00.33  0.1  6408 4848 2572 S /etc/authlib/authProg
     1392 root      16   0    0   0:00.17  0.1  6408 4908 2636 S /etc/authlib/authProg
     1393 root      17   0    0   0:00.17  0.1  6408 4908 2636 S /etc/authlib/authProg
     1394 root      16   0    0   0:00.14  0.1  6408 4908 2636 S /etc/authlib/authProg
     1396 root      16   0    0   0:00.24  0.1  6408 4844 2572 S /etc/authlib/authProg
     5279 root      17   0    0   0:00.02  0.0  5888 1348 1048 S pure-ftpd (SERVER)
     5283 root      18   0    0   0:00.00  0.0  3580  924  728 S /usr/sbin/pure-authd -s /var/run/ftpd.sock -r /usr/sbin/pureauth
     5326 root      16   0    0   0:02.34  0.1  7848 5996  904 S lfd - sleeping
     5458 root      18   0    0   0:00.00  0.0  3580  920  724 S /usr/sbin/pure-authd -s /var/run/ftpd.sock -r /usr/sbin/pureauth
     5477 root      17   0    0   0:00.03  0.0  2484  916  524 S crond
     5871 xfs       16   0    0   0:00.00  0.0  3036 1332  756 S xfs -droppriv -daemon
     7858 root      16   0    0   0:01.27  0.1  100m  11m 4676 S /usr/local/apache/bin/httpd -DSSL
     9277 root      18   0    0   0:00.00  0.1 13660 7884  360 S cpdavd - accepting connections on 2077 and 2078
     9546 root      15   0    0   0:00.50  0.0  6024 3496 **** S cpbandwd
     9547 root      34  19    0   0:01.41  0.1  9824 5348 1792 S cpanellogd - sleeping for logs
     9698 root      18   0    0   0:00.00  0.0  4060  752  568 S /usr/sbin/saslauthd -m /var/run/saslauthd -a pam -n 1
     9857 dbus      16   0    0   0:00.00  0.0  2400  876  784 S dbus-daemon-1 --system
     9956 root      16   0    0   0:00.22  0.1 18584 9060 1004 S cpsrvd - waiting for connections
    10008 root      18   0    0   0:00.00  0.0  1488  392  320 S /usr/sbin/portsentry -tcp
    10074 root      18   0    0   0:00.00  0.0  3580  728  724 S /usr/sbin/pure-authd -s /var/run/ftpd.sock -r /usr/sbin/pureauth

  2. #27
    this is what i see on another VPS:

    Code:
    top - 08:54:31 up  1:44,  1 user,  load average: 8.61, 11.09, 13.53
    Tasks: 101 total,   5 running,  94 sleeping,   0 stopped,   2 zombie
    Cpu(s):  1.1% us,  0.6% sy,  0.0% ni, 45.3% id, 53.0% wa,  0.0% hi,  0.0% si
    Mem:   8298896k total,  8187672k used,   111224k free,   108460k buffers
    Swap:  8385920k total,  2032644k used,  6353276k free,  2437592k cached
      PID USER      PR  NI %CPU    TIME+  %MEM  VIRT  RES  SHR S COMMAND
    29986 root      15   0    0   0:00.00  0.0  1804  360  240 S /usr/libexec/courier-authlib/authdaemond
    29987 root      15   0    0   0:00.00  0.0  1804  360  240 S /usr/libexec/courier-authlib/authdaemond
    29989 root      15   0    0   0:00.00  0.0  1804  360  240 S /usr/libexec/courier-authlib/authdaemond
    29990 root      16   0    0   0:00.00  0.0  1804  360  240 S /usr/libexec/courier-authlib/authdaemond
    29991 root      15   0    0   0:00.00  0.0  1804  360  240 S /usr/libexec/courier-authlib/authdaemond
    30110 root      16   0    0   0:00.00  0.0  4024 1032  740 S /usr/sbin/sshd
    30150 root      18   0    0   0:00.00  0.0  2084  780  652 S xinetd -stayalive -pidfile /var/run/xinetd.pid
    30191 root      20   0    0   0:00.00  0.0  2152 1120  956 S /bin/sh /usr/bin/mysqld_safe --datadir=/var/lib/mysql --pid-file=/var/lib/mysql/server.otherserver.com.pid
    30229 mysql     16   0    0   0:00.78  0.3  180m  23m 3396 S /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/server.an-dns5.com.pid --skip-external-locking --port
    30537 root      15   0    0   0:00.13  0.0  5672 4116 1216 S chkservd
    30550 root      16   0    0   0:00.00  0.0  1460  380  320 S /usr/sbin/courierlogger -pid=/var/run/imapd.pid -start -name=imapd /usr/lib/courier-imap/libexec/couriertcpd -address=0 -maxprocs=100 -maxperip=50
    30551 root      16   0    0   0:00.01  0.0  1568  516  440 S /usr/lib/courier-imap/libexec/couriertcpd -address=0 -maxprocs=100 -maxperip=50 -nodnslookup -noidentlookup 143 /usr/lib/courier-imap/sbin/imaplog
    30564 root      16   0    0   0:00.00  0.0  1460  380  320 S /usr/sbin/courierlogger -pid=/var/run/imapd-ssl.pid -start -name=imapd-ssl /usr/lib/courier-imap/libexec/couriertcpd -address=0 -maxprocs=100 -max
    30565 root      16   0    0   0:00.00  0.0  1568  516  440 S /usr/lib/courier-imap/libexec/couriertcpd -address=0 -maxprocs=100 -maxperip=50 -nodnslookup -noidentlookup 993 /usr/lib/courier-imap/bin/couriert
    30571 root      16   0    0   0:00.05  0.0  1460  380  320 S /usr/sbin/courierlogger -pid=/var/run/pop3d.pid -start -name=pop3d /usr/lib/courier-imap/libexec/couriertcpd -address=0 -maxprocs=100 -maxperip=50
    30572 root      16   0    0   0:00.06  0.0  1568  516  440 S /usr/lib/courier-imap/libexec/couriertcpd -address=0 -maxprocs=100 -maxperip=50 -nodnslookup -noidentlookup 110 /usr/lib/courier-imap/sbin/pop3log
    30577 root      15   0    0   0:00.00  0.0  1460  380  320 S /usr/sbin/courierlogger -pid=/var/run/pop3d-ssl.pid -start -name=pop3d-ssl /usr/lib/courier-imap/libexec/couriertcpd -address=0 -maxprocs=100 -max
    30578 root      17   0    0   0:00.00  0.0  1568  516  440 S /usr/lib/courier-imap/libexec/couriertcpd -address=0 -maxprocs=100 -maxperip=50 -nodnslookup -noidentlookup 995 /usr/lib/courier-imap/bin/couriert
    32497 root      15   0    0   0:25.33  0.9  113m  69m  924 S /usr/sbin/clamd
    32510 mailnull  16   0    0   0:01.46  0.0  7480 1192  784 S /usr/sbin/exim -bd -q60m
    32526 mailnull  20   0    0   0:00.00  0.0  7684 1132  728 S /usr/sbin/exim -tls-on-connect -bd -oX 465
    32571 root      15   0    0   0:00.73  0.0  3784 1752  640 S antirelayd
     1421 root      16   0    0   0:00.39  0.1  6408 4920 2636 S /etc/authlib/authProg
     1422 root      16   0    0   0:00.27  0.1  6408 4908 2628 S /etc/authlib/authProg
     1538 root      15   0    0   0:00.31  0.1  6408 4848 2564 S /etc/authlib/authProg
     3955 root      16   0    0   0:00.22  0.1  6408 4912 2628 S /etc/authlib/authProg
     5138 root      15   0    0   0:00.01  0.0  5888 1348 1048 S pure-ftpd (SERVER)
     5143 root      17   0    0   0:00.00  0.0  3580  916  720 S /usr/sbin/pure-authd -s /var/run/ftpd.sock -r /usr/sbin/pureauth
     5322 root      15   0    0   0:00.80  0.3 27544  24m 1936 S /usr/bin/spamd -d --allowed-ips=127.0.0.1 --pidfile=/var/run/spamd.pid --max-children=5
     5406 root      15   0    0   0:01.90  0.1  7980 6084  904 S lfd - sleeping
     5797 username  15   0    0   0:20.91  0.4 32032  28m 2044 S spamd child
     7376 root      15   0    0   0:00.98  0.2 88080  12m 4916 S /usr/local/apache/bin/httpd -DSSL
     7417 root      18   0    0   0:00.00  0.0  3580  912  716 S /usr/sbin/pure-authd -s /var/run/ftpd.sock -r /usr/sbin/pureauth
     7446 root      15   0    0   0:00.04  0.0  2484  920  524 S crond
     7906 xfs       16   0    0   0:00.00  0.0  3036 1332  756 S xfs -droppriv -daemon
    10121 root      18   0    0   0:00.00  0.1 13660 6092  360 S cpdavd - accepting connections on 2077 and 2078
    10206 root      16   0    0   0:00.35  0.1 18584 9060 1004 S cpsrvd - waiting for connections
    11383 root      15   0    0   0:00.67  0.1  6024 4344 **** S cpbandwd
    Last edited by reamark; 03-21-2008 at 05:36 AM.

  3. #28
    and this is the 3° VPS:
    Code:
    top - 08:55:54 up  1:46,  1 user,  load average: 8.11, 10.91, 13.48
    Tasks:  87 total,   1 running,  86 sleeping,   0 stopped,   0 zombie
    Cpu(s):  1.7% us,  0.8% sy,  0.0% ni, 31.5% id, 66.1% wa,  0.0% hi,  0.0% si
    Mem:   8298896k total,  8234664k used,    64232k free,   128220k buffers
    Swap:  8385920k total,  2032640k used,  6353280k free,  2507816k cached
      PID USER      PR  NI %CPU    TIME+  %MEM  VIRT  RES  SHR S COMMAND
    28166 mysql     15   0    1   6:23.70  0.3  116m  20m 3560 S /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/server.myserver.com.pid --skip-external-locking --port
     5564 nobody    16   0    1   0:22.57  0.3  110m  22m 9904 S /usr/local/apache/bin/httpd -DSSL
    25806 mailnull  15   0    1   0:00.03  0.0 10112 4008 2684 S /usr/sbin/exim -bd -q60m
    25820 mailnull  16   0    1   0:00.02  0.0 10112 3972 2652 D /usr/sbin/exim -bd -q60m
    25822 mailnull  16   0    1   0:00.02  0.0 10112 3984 2664 D /usr/sbin/exim -bd -q60m
    25880 root      18   0    1   0:00.02  0.0  9420 4148 2844 S /usr/sbin/exim -Mc 1Jcc6m-0006gx-OV
    25616 named     19   0    0   0:18.15  0.1 78016  12m 1944 S /usr/sbin/named -u named
     3158 root      16   0    0   0:00.63  0.0  7068 2308 1840 S sshd: root@pts/0
     7256 root      15   0    0   0:00.92  0.0  2024 1072  788 R top
    22263 root      15   0    0   0:00.09  0.0  1896 1016  788 S top -c
        1 root      16   0    0   0:00.07  0.0  1628  604  524 S init [3]
    24528 root      15   0    0   0:00.40  0.0  1532  528  440 S syslogd -m 0
    28065 root      15   0    0   0:00.00  0.0  1456  376  320 S /usr/sbin/courierlogger -pid=/var/spool/authdaemon/pid -facility=mail -start /usr/libexec/courier-authlib/authdaemond
    28066 root      16   0    0   0:00.00  0.0  1804  592  484 S /usr/libexec/courier-authlib/authdaemond
    28075 root      16   0    0   0:00.02  0.0  5764 1784 1360 S cupsd
    28080 root      16   0    0   0:00.01  0.0  1804  360  240 S /usr/libexec/courier-authlib/authdaemond
    28081 root      15   0    0   0:00.01  0.0  1804  360  240 S /usr/libexec/courier-authlib/authdaemond
    28082 root      16   0    0   0:00.01  0.0  1804  360  240 S /usr/libexec/courier-authlib/authdaemond
    28083 root      16   0    0   0:00.00  0.0  1804  360  240 S /usr/libexec/courier-authlib/authdaemond
    28084 root      15   0    0   0:00.01  0.0  1804  360  240 S /usr/libexec/courier-authlib/authdaemond
    28085 root      16   0    0   0:00.01  0.0  1804  360  240 S /usr/libexec/courier-authlib/authdaemond
    28086 root      16   0    0   0:00.01  0.0  1804  360  240 S /usr/libexec/courier-authlib/authdaemond
    28088 root      15   0    0   0:00.01  0.0  1804  360  240 S /usr/libexec/courier-authlib/authdaemond
    28089 root      16   0    0   0:00.01  0.0  1804  360  240 S /usr/libexec/courier-authlib/authdaemond
    28090 root      15   0    0   0:00.00  0.0  1804  360  240 S /usr/libexec/courier-authlib/authdaemond
    28115 root      17   0    0   0:00.14  0.0  4028 1136  840 S /usr/sbin/sshd
    28126 root      17   0    0   0:00.00  0.0  2084  784  652 S xinetd -stayalive -pidfile /var/run/xinetd.pid
    28135 root      17   0    0   0:00.00  0.0  2152 1120  956 S /bin/sh /usr/bin/mysqld_safe --datadir=/var/lib/mysql --pid-file=/var/lib/mysql/server..com.pid
    28225 root      15   0    0   0:00.08  0.0  5672 4112 1216 S chkservd
    29827 mailnull  16   0    0   0:00.00  0.0  8552 1168  776 S /usr/sbin/exim -bd -oX 26
    29833 mailnull  16   0    0   0:02.22  0.0  9028 1200  792 S /usr/sbin/exim -bd -q60m
    29837 mailnull  22   0    0   0:00.00  0.0  8308 1144  752 S /usr/sbin/exim -tls-on-connect -bd -oX 465
    29845 root      15   0    0   0:01.76  0.0  3784 1764  640 S antirelayd
    29856 root      15   0    0   0:00.59  0.1  6408 4956 2636 S /etc/authlib/authProg
    29906 root      16   0    0   0:00.62  0.1  6408 4960 2636 S /etc/authlib/authProg
    29958 root      16   0    0   0:00.47  0.1  6408 4960 2636 S /etc/authlib/authProg
     1349 root      16   0    0   0:00.37  0.1  6408 4960 2636 S /etc/authlib/authProg
     1705 root      17   0    0   0:00.01  0.0  5888 1348 1048 S pure-ftpd (SERVER)
     1719 root      18   0    0   0:00.00  0.0  3580  924  728 S /usr/sbin/pure-authd -s /var/run/ftpd.sock -r /usr/sbin/pureauth
     1788 root      15   0    0   0:01.17  0.3 27524  24m 1936 S /usr/bin/spamd -d --allowed-ips=127.0.0.1 --pidfile=/var/run/spamd.pid --max-children=5
     1932 root      15   0    0   0:00.85  0.1  6452 5060 2724 S /etc/authlib/authProg
     1960 root      18   0    0   0:00.00  0.0  3580  920  724 S /usr/sbin/pure-authd -s /var/run/ftpd.sock -r /usr/sbin/pureauth
     1989 root      16   0    0   0:00.03  0.0  2484  916  524 S crond
     3419 xfs       15   0    0   0:00.00  0.0  3036 1332  756 S xfs -droppriv -daemon
     5269 root      15   0    0   0:01.70  0.1  102m  11m 4808 S /usr/local/apache/bin/httpd -DSSL
     5365 root      18   0    0   0:00.00  0.1 13660 7900  360 S cpdavd - accepting connections on 2077 and 2078
     5562 nobody    15   0    0   0:22.37  0.3  105m  21m  11m S /usr/local/apache/bin/httpd -DSSL
     5565 nobody    15   0    0   0:17.80  0.3  108m  22m  11m S /usr/local/apache/bin/httpd -DSSL
     5566 nobody    16   0    0   0:14.23  0.3  106m  24m  13m S /usr/local/apache/bin/httpd -DSSL
     5568 nobody    15   0    0   0:26.86  0.2  107m  17m 8200 S /usr/local/apache/bin/httpd -DSSL
     5773 nobody    15   0    0   0:25.60  0.3  110m  27m  14m S /usr/local/apache/bin/httpd -DSSL
     5801 root      15   0    0   0:01.83  0.1  6028 4416 **** S cpbandwd
     5802 root      34  19    0   0:01.76  0.1  9756 6912 1688 S cpanellogd - sleeping for logs
     5861 root      18   0    0   0:00.00  0.0  4060  796  568 S /usr/sbin/saslauthd -m /var/run/saslauthd -a pam -n 1
     5976 root      16   0    0   0:00.14  0.1 18584 9060 1004 S cpsrvd - waiting for connections

  4. #29
    Join Date
    Dec 2003
    Location
    Hamilton, NJ, USA
    Posts
    1
    This may be caused by someone running a backup of their node from the VPS Power Panel. I've had support kill my backup jobs because they were affecting other users on the node. (The backup runs at the host level, not the VPS level). I only run that backup once a month or so now, and I run it in the middle of the night.

    The problem is really with Virtuozzo (and VPSs in general)...They do a good job of separating the individual nodes, but if something is running on the layer above (the host machine), it can affect all of the nodes,

  5. #30
    Hello Ron,

    I wonder if your problem was resolved at all. I'm on slhost too for about 8 month. In general it is an excellent hosting, but currently I have exactly the same high-load VPS problem, it happens each day, near 9:00 GMT.

    Regards,
    Mikhail

  6. #31
    Join Date
    Mar 2007
    Location
    United Kingdom
    Posts
    207
    Quote Originally Posted by rfulkerson View Post
    Is this what I can expect from all VPS plans? Do I just have live with it, or would another host (possibly Xen based) be better?
    No, VPS plans aren't like this in general - it's a symptom of an overloaded node. An experienced VZ provider can identify the VPS's causing high load and re-balance their nodes so that the disk I/O problem disappears (i.e. your VPS is moved to another node, or the problem VPS(s) are moved elsewhere onto a node which has less I/O usage and/or higher I/O capacity).

    The technology used isn't to blame, and I would be careful about assuming VZ or Xen (etc.) would do a better job or otherwise as you really need to understand the technology in detail to make that level of judgement. There are advantages and disadvantages of each virtualisation technology but any will potentially work ok for you with a provider that handles it properly.

    Quote Originally Posted by devonblzx View Post
    The differences between Xen and VZ would not be noticed in this situation. This could happen anywhere I suppose, but if it is a persistent problem caused by the main node then KnownHost should be able to track down the usage and find which VPS is causing the problem.
    Exactly. It's very easy for the provider to evaluate this situation and IMO it's not appropriate to expect the customer to do all of the detective work (even if it's an unmanaged VPS) - if the load is coming from the node (i.e. due to I/O problems) then it's for the provider to identify and resolve as it's not a problem within the VPS.

    In this case, I'm surprised they haven't moved your VPS onto a different node as a "let's see what happens" kind of idea. At least that way they would probably have resolved your problems - even if they didn't understand why

  7. #32
    Join Date
    Jul 2005
    Location
    Australia
    Posts
    105
    I am having the exact problem as rfulkerson is having...also Slhost has shifted me onto another node, but I still have high loads on the server starting at 4.00 pm {Aussie Time} approx...and sometimes going on for an hour or so, I have been with them for over 2 years..and never have had these problems before...but the last few months have been shocking

    Every time they check the server, they report back everything is fine, they also stated that backs up on the node can cause these problems, well then they should be doing something about it, my sites are very low resources, so they would not be causing any problem with load.

  8. #33
    Join Date
    Jan 2006
    Posts
    1,922
    Quote Originally Posted by devonblzx View Post
    The differences between Xen and VZ would not be noticed in this situation. This could happen anywhere I suppose, but if it is a persistent problem caused by the main node then KnownHost should be able to track down the usage and find which VPS is causing the problem.

    The only reason the VPS load average would go up because of the node is because it is waiting for disk, that is why I said to open up top and see where the usage is. If their is a lot of CPU under the wait (wa) category then the problem is being caused by the main node's disks. If not, then their could also be a problem within your VPS.

    Is this a managed VPS? If so, they should track it down for you, if not, you may want to look into a managed solution if it does not resolve.
    This thread is a bit old but I noticed KnownHost mentioned. I think this thread was about SLhost not KnownHost unless I am missing something. We always move a customer to another node if it seems to be the best option at that time.

    -Jay
    KnownHost Managed VPS Specialists
    Toll Free: (866)-332-9894
    Fully Managed VPS, Wordpress, Cloud Servers, and Dedicated Servers

  9. #34
    Join Date
    Jul 2005
    Location
    Australia
    Posts
    105
    You are correct Knownhost...It is about Slhost, I say it is a typo error regarding your company...in which I have heard good reports about

  10. #35
    Join Date
    Jan 2006
    Posts
    1,922
    Quote Originally Posted by Unix-Aussie.Host View Post
    You are correct Knownhost...It is about Slhost, I say it is a typo error regarding your company...in which I have heard good reports about
    Thank you. We do try. I figured it was a typo but wanted to make sure.

    -Jay
    KnownHost Managed VPS Specialists
    Toll Free: (866)-332-9894
    Fully Managed VPS, Wordpress, Cloud Servers, and Dedicated Servers

  11. #36
    as mentioned elswhere i also had this high load on some VPS i have with slhost since February (sometimes it goes up to 30. ) Some VPS has be transfered to other nodes and it's a bit better now. I think they growing and just hosted to many VPS on the same node.

  12. #37
    Join Date
    Jun 2008
    Location
    India
    Posts
    266
    you may use sar command with opetions

  13. #38
    Quote Originally Posted by rankris View Post
    you may use sar command with opetions
    can you elaborate please?

    thanks

  14. #39
    Join Date
    Feb 2006
    Location
    Portland, Oregon
    Posts
    3
    I'm about 5 months into my 3rd year with slhost.

    Things were good for the first two years. But since the first of THIS year, I've had nothing but problems with cpus running way high and, of course, pages not loading till next week.

    I've sent countless support tickets to SL host. And they DO reply back fairly quickly... but never resolve the problem once and for all. Initially, support tried to pass it off as MY vps issue. But not a thing has changed with sites on my vps since before the first of the year. Sites are low traffic, with no scripts or anything fancy running in the background... no cron jobs... nuttin.

    Then, slightly over a month ago they migrated my vps to another datacenter - without giving me any notice. I found out when I arrived at my computer one morning to find ALL SITES dead, and couldn't log into any cpanels or WHM. Support replied with my NEW IP. But NOT the new login/password. Sheesh... Finally got that ironed out. But...

    Since that migration, I've been having to restart Apache 3-4 or MORE times a day just to get cpus down low enough for pages to finally load.

    I submitted a ticket to sales last week saying that I canNOT continue to spend an hour or more per day with SLHost support and restarting apache, and that I'm going to be moving out unless they do something. They replied back four days ago saying they were
    1. Unaware of this problem and
    2. They are moving my vps to a new server and that will fix the problem.

    Well, it's day 4, and I've not been notified that they've moved my vps to a less crowded server. And, I get to my computer this morning to find NO sites loading and cpus over 16.75

    Sent another support ticket, and I get this reply...

    ~~~~~~~~~~~~~~~~
    Service apache was causing heavy load on your server and I have turned it for you. The load has been brought down to normal levels and your domains are loading fine atm. Please have a check and update us if there are still problems.

    Update us incase you face the same issue again in future and we will have it investigated for you.
    ~~~~~~~~~~~~~~~~~~~~~~~~

    Good grief! What has happened to SL Host? You'd think with over a dozen support tickets lodged for this SAME issue - And now I've gotten SALES department in on this... That they'd quit with the 'canned, stupid' replies. And DO SOMETHING.

    Worst of it all is I PAY once yearly. And I JUST paid for my
    3rd year in full the end of March. And they tell me they do NOT offer refunds after 30 days. You'd think SL Host would treat a long-time, yearly paying customer better than this!

    ARGH!! I'm giving them till Monday evening. Then my only logical and smart choice is to move 'outa there. Losing the pre-paid year's hosting fee is getting to be a moot point, considering the revenue I've lost just in the last 4 weeks with slow to no page loads.

    I've got a VPS at KnownHost - slightly more expense but always stellar performance. I'll either get a 2nd account at KH and migrate over there, or I'm also considering Servint or WiredTree.

    Deb

  15. #40
    Join Date
    Jan 2006
    Posts
    1,922
    Quote Originally Posted by oppgroup View Post
    I'm about 5 months into my 3rd year with slhost.

    Things were good for the first two years. But since the first of THIS year, I've had nothing but problems with cpus running way high and, of course, pages not loading till next week.

    I've sent countless support tickets to SL host. And they DO reply back fairly quickly... but never resolve the problem once and for all. Initially, support tried to pass it off as MY vps issue. But not a thing has changed with sites on my vps since before the first of the year. Sites are low traffic, with no scripts or anything fancy running in the background... no cron jobs... nuttin.

    Then, slightly over a month ago they migrated my vps to another datacenter - without giving me any notice. I found out when I arrived at my computer one morning to find ALL SITES dead, and couldn't log into any cpanels or WHM. Support replied with my NEW IP. But NOT the new login/password. Sheesh... Finally got that ironed out. But...

    Since that migration, I've been having to restart Apache 3-4 or MORE times a day just to get cpus down low enough for pages to finally load.

    I submitted a ticket to sales last week saying that I canNOT continue to spend an hour or more per day with SLHost support and restarting apache, and that I'm going to be moving out unless they do something. They replied back four days ago saying they were
    1. Unaware of this problem and
    2. They are moving my vps to a new server and that will fix the problem.

    Well, it's day 4, and I've not been notified that they've moved my vps to a less crowded server. And, I get to my computer this morning to find NO sites loading and cpus over 16.75

    Sent another support ticket, and I get this reply...

    ~~~~~~~~~~~~~~~~
    Service apache was causing heavy load on your server and I have turned it for you. The load has been brought down to normal levels and your domains are loading fine atm. Please have a check and update us if there are still problems.

    Update us incase you face the same issue again in future and we will have it investigated for you.
    ~~~~~~~~~~~~~~~~~~~~~~~~

    Good grief! What has happened to SL Host? You'd think with over a dozen support tickets lodged for this SAME issue - And now I've gotten SALES department in on this... That they'd quit with the 'canned, stupid' replies. And DO SOMETHING.

    Worst of it all is I PAY once yearly. And I JUST paid for my
    3rd year in full the end of March. And they tell me they do NOT offer refunds after 30 days. You'd think SL Host would treat a long-time, yearly paying customer better than this!

    ARGH!! I'm giving them till Monday evening. Then my only logical and smart choice is to move 'outa there. Losing the pre-paid year's hosting fee is getting to be a moot point, considering the revenue I've lost just in the last 4 weeks with slow to no page loads.

    I've got a VPS at KnownHost - slightly more expense but always stellar performance. I'll either get a 2nd account at KH and migrate over there, or I'm also considering Servint or WiredTree.

    Deb
    SLHost sold their company from what I heard. I think there was a thread in the outages forum about it recently. Also, it's great to hear your happy with us.

    -Jay
    KnownHost Managed VPS Specialists
    Toll Free: (866)-332-9894
    Fully Managed VPS, Wordpress, Cloud Servers, and Dedicated Servers

  16. #41
    Join Date
    Feb 2006
    Location
    Portland, Oregon
    Posts
    3
    Yeah, Jay... pretty happy I AM.

    I've learned since the 1st of this year that it doesn't matter HOW MUCH Ram and Bandwidth a plan says it offers if they Oversell or overload the server. Same with price - what good is saving money if your site pages can't load for viewing.

    And I guess the fact that SLHost was sold may explain why their service/performance has taken a huge dump in the toilet. ;-)

    Thanks for that info.

    Deb

  17. #42
    Join Date
    Jan 2006
    Posts
    1,922
    Quote Originally Posted by oppgroup View Post
    Yeah, Jay... pretty happy I AM.

    I've learned since the 1st of this year that it doesn't matter HOW MUCH Ram and Bandwidth a plan says it offers if they Oversell or overload the server. Same with price - what good is saving money if your site pages can't load for viewing.

    And I guess the fact that SLHost was sold may explain why their service/performance has taken a huge dump in the toilet. ;-)

    Thanks for that info.

    Deb
    Well, we would love to continue servicing you for any additional needs. It's a pleasure working with you.

    -Jay

  18. #43
    Join Date
    Sep 2005
    Location
    Canada
    Posts
    646
    When the support staff reply with bad grammar and kill apache on your server its time to move on
    VPSVille.com
    Toronto, London, Dallas, Los Angeles
    Quality VPS hosting on Premium bandwidth

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •