Hi,
It depends on the threading library you use. Can you please
show us the output of
ldd /usr/local/libexec/mysqld ?
You should use libthr instead of libpthread or libc_r in /etc/libmap.conf
for mysqld.
--
Martin
Martin Blapp, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
------------------------------------------------------------------
ImproWare AG, UNIXSP & ISP, Zurlindenstrasse 29, 4133 Pratteln, CH
Phone: +41 61 826 93 00 Fax: +41 61 826 93 01
PGP: <finger -l [EMAIL PROTECTED]>
PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E
------------------------------------------------------------------
On Fri, 11 May 2007, Abdullah Ibn Hamad Al-Marri wrote:
Hello,
I have dual xeon server with 2 GB of ram.
FreeBSD 6.2-STABLE #0: Tue Apr 24 11:32:50 GMT 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/NOC i386
Which runs heavily MySQL with MyISAM, the problem I have it maxes out
one cpu, and doesn't use the other one.
Could someone tell me what shall I do to make MySQL runs faster? it
already uses libthr, cache beside MySQL optimized, I would like to use
the power of both cpus.
last pid: 79040; load averages: 1.00, 1.01, 1.00
up 16+16:54:20 08:04:55
39 processes: 2 running, 37 sleeping
CPU states: 26.9% user, 0.0% nice, 23.3% system, 0.0% interrupt, 49.8% idle
Mem: 556M Active, 1154M Inact, 198M Wired, 93M Cache, 112M Buf, 3072K Free
Swap: 5120M Total, 16K Used, 5120M Free
PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND
90293 mysql 19 100 0 434M 187M ucond 1 176.6H 95.95% mysqld
Is upgrading to FreeBSD 7.0 current and using ULE would make MySQL
runs in this dual xeon box?
--
Regards,
-Abdullah Ibn Hamad Al-Marri
Arab Portal
http://www.WeArab.Net/
_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
