Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 12 Mar 2002 09:08:05 +0100
From:      "Bob Kersten" <bob@fellownet.org>
To:        "Bill Moran" <wmoran@potentialtech.com>
Cc:        <freebsd-stable@freebsd.org>
Subject:   Re: crontab and mysql
Message-ID:  <002901c1c99d$0db0e5f0$2849a8c0@kerstenz6r4278>
References:  <001e01c1c942$d5f25ea0$0200000a@alpha> <3C8D57E3.6050403@potentialtech.com>

next in thread | previous in thread | raw e-mail | index | archive | help
> Can you watch "top" and "systat" (the vmstat screen) while
> these delays are occurring?

Nothing weird there. mysqld and httpd are both using not more than 15%
processor capacity. I've sorted 'top' using the time column, and
mysqld is listed on top (that proves that it is indeed using way too
much time to do it's job):

last pid: 21365;  load averages:  0.01,  0.10,  0.06    up 1+14:29:17
09:
27 processes:  1 running, 26 sleeping
CPU states:  2.3% user,  0.0% nice,  0.4% system,  0.4% interrupt,
97.0% i
Mem: 23M Active, 5500K Inact, 14M Wired, 4848K Cache, 14M Buf, 12M
Free
Swap: 113M Total, 88K Used, 113M Free

  PID USERNAME PRI NICE  SIZE    RES STATE    TIME   WCPU    CPU
COMMAND
  132 mysql      2   0 19840K  7188K poll    15:01  0.00%  0.00%
mysqld
   60 root       2   0   504K   272K select   1:33  0.00%  0.00% natd
  284 nobody     2   0  3744K  2912K accept   1:30  0.00%  0.00% httpd
  149 nobody     2   0  3876K  2972K accept   1:04  0.00%  0.00% httpd
  131 nobody     2   0  4328K  3492K accept   0:44  0.00%  0.00% httpd
  130 nobody     2   0  4008K  3144K accept   0:42  0.00%  0.00% httpd
  129 nobody     2   0  4272K  3448K accept   0:42  0.00%  0.00% httpd
  148 nobody     2   0  3976K  3136K accept   0:35  0.00%  0.00% httpd
  128 root       2   0  3112K  1724K select   0:24  0.00%  0.00% httpd
   85 root       2   0  2596K  1276K select   0:12  0.00%  0.00% sshd
12737 root       2   0  2320K  1152K select   0:11  0.00%  0.00%
telnetd
   73 root       2   0   964K   560K select   0:06  0.00%  0.00%
syslogd
   83 root      10   0  1004K   620K nanslp   0:06  0.00%  0.00% cron
21365 root      28   0  1908K  1056K RUN      0:04  1.81%  1.81% top
21343 root       2   0  2320K  1384K select   0:02  0.00%  0.00%
telnetd
12740 root       3   0  1312K   880K ttyin    0:02  0.00%  0.00% csh
  294 root       3   0  1328K   880K ttyin    0:02  0.00%  0.00% csh
21346 root      18   0  1328K   900K pause    0:01  0.00%  0.00% csh
  108 root      10   0   644K   248K wait     0:00  0.00%  0.00% sh
21344 root      10   0  1216K   852K wait     0:00  0.00%  0.00% login
  293 root      10   0  1216K   784K wait     0:00  0.00%  0.00% login
12738 root      10   0  1216K   788K wait     0:00  0.00%  0.00% login
21345 bob       10   0   636K   252K wait     0:00  0.00%  0.00% sh
12739 bob       10   0   636K   252K wait     0:00  0.00%  0.00% sh
 9191 root       3   0   948K   572K ttyin    0:00  0.00%  0.00% getty
   81 root       2   0  1072K   624K select   0:00  0.00%  0.00% inetd
   23 root      18   0   208K    60K pause    0:00  0.00%  0.00%
adjkerntz

> Simply the size of the db isn't enough to diagnose.
> Do you have it well indexed, and are you searching
> on indexed columns? Lots of factors that could affect
> this. Was php compiled into Apache statically or as a
> module?

Let's see, I have indexes on all columns that I use to limit a
resultset or search rows on. I've compiled PHP statically in apache
and I've included the mysql path in the --with-mysql=... option. I've
used the most recent sources of PHP, Apache and MySQL.

Can you do something with this information?

Thnx,
 Bob.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002901c1c99d$0db0e5f0$2849a8c0>