Thanks, Arjen. That is interesting about linux "threads" showing up as separate
processes. They each have separate PID's, so I am guessing that it really doesn't
matter what you call it; each thread still takes up the same amount of memory as
the 'ps' command reports. In my case:
# ps vaw |grep mysqld
PID TTY STAT TIME MAJFL TRS DRS RSS %MEM COMMAND
5012 pts/5 S 0:00 235 505 1706 4 0.0 /bin/sh ./bin/mysqld_safe
--datadir=/usr/local/mysql/data --pid-file=/usr/lo
5037 pts/5 S 0:11 16341 3577 20830 1308 5.1 /usr/local/mysql/bin/mysqld
--defaults-extra-file=/usr/local/mysql/data/my.c
5039 pts/5 S 0:07 2237 3577 20830 1308 5.1 /usr/local/mysql/bin/mysqld
--defaults-extra-file=/usr/local/mysql/data/my.c
5040 pts/5 S 0:00 2 3577 20830 1308 5.1 /usr/local/mysql/bin/mysqld
--defaults-extra-file=/usr/local/mysql/data/my.c
5041 pts/5 S 0:00 0 3577 20830 1308 5.1 /usr/local/mysql/bin/mysqld
--defaults-extra-file=/usr/local/mysql/data/my.c
5042 pts/5 S 0:00 1 3577 20830 1308 5.1 /usr/local/mysql/bin/mysqld
--defaults-extra-file=/usr/local/mysql/data/my.c
5043 pts/5 S 0:00 0 3577 20830 1308 5.1 /usr/local/mysql/bin/mysqld
--defaults-extra-file=/usr/local/mysql/data/my.c
5044 pts/5 S 0:00 1 3577 20830 1308 5.1 /usr/local/mysql/bin/mysqld
--defaults-extra-file=/usr/local/mysql/data/my.c
5045 pts/5 S 0:26 10873 3577 20830 1308 5.1 /usr/local/mysql/bin/mysqld
--defaults-extra-file=/usr/local/mysql/data/my.c
5046 pts/5 S 0:00 15 3577 20830 1308 5.1 /usr/local/mysql/bin/mysqld
--defaults-extra-file=/usr/local/mysql/data/my.c
5047 pts/5 S 0:03 1419 3577 20830 1308 5.1 /usr/local/mysql/bin/mysqld
--defaults-extra-file=/usr/local/mysql/data/my.c
# top
8:45pm up 6 days, 3:52, 8 users, load average: 0.06, 0.17, 0.17
84 processes: 82 sleeping, 2 running, 0 zombie, 0 stopped
CPU states: 6.6% user, 5.4% system, 0.0% nice, 87.9% idle
Mem: 25468K av, 24268K used, 1200K free, 0K shrd, 2544K buff
Swap: 65528K av, 28484K used, 37044K free 8604K cached
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND
5045 mysql 10 0 10384 1336 660 S 0.1 5.2 0:26 mysqld
5037 mysql 9 0 10384 1336 660 S 0.0 5.2 0:11 mysqld
5039 mysql 9 0 10384 1336 660 S 0.0 5.2 0:07 mysqld
5040 mysql 9 0 10384 1336 660 S 0.0 5.2 0:00 mysqld
5041 mysql 9 0 10384 1336 660 S 0.0 5.2 0:00 mysqld
5042 mysql 9 0 10384 1336 660 S 0.0 5.2 0:00 mysqld
5043 mysql 9 0 10384 1336 660 S 0.0 5.2 0:00 mysqld
5044 mysql 9 0 10384 1336 660 S 0.0 5.2 0:00 mysqld
5046 mysql 9 0 10384 1336 660 S 0.0 5.2 0:00 mysqld
5047 mysql 9 0 10384 1336 660 S 0.0 5.2 0:03 mysqld
5012 root 9 0 184 4 0 S 0.0 0.0 0:00 mysqld_safe
So isn't each of the ten (10) processes using 10384 K, for a total of
103840 K? If so, this seems excessive, don't you think, considering my
32 M of RAM and two or three concurrent connections?
On Thu, Nov 13, 2003 at 11:17:33AM +1000, Arjen Lentz wrote:
> The
> connection-specific variables can be adjusted.
> You can also set the maximum # of connections the server will allow.
Can you suggest *which* variables to try changing? I already tried
'thread_concurrency', but this did not take effect -- we still got ten
threads on the 'ps' / 'top' report.
Also, do you know, if we set this variable to, say, 2, then
will mysqld automatically increase it if necessary? E.g. like apache
does with its children.
Thanks again for your insights.
Regards,
George Webb
[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
