Hi!
People are reporting performance problems also from the FreeBSD port of
Innobase. There seems to be a runaway thread which gets free sometimes
and eats up 100 % of the CPU. It was not fixed with the latest patches to
Innobase.
I will try setting thread priorities in 3.23.37. That might help, but I
guess the
real reason is different. I will probably finish my work on 37 today and
tomorrow I will try to repeat the problems on our FreeBSD computer.
Regards,
Heikki
>Johan Andersson writes:
>> I've had the same problem on an Intel P-III 800 w 256M RAM running
FreeBSD 4.1-RELEASE
>with
>> both the distribution from the ports tree and the source dist. from
mysql.com.
>>
>> I tried to solve the problem with analysing all the database traffic, but
mysql
>were taking all free CPU
>> that were availble on the same database traffic (same database) that were
running
>fine on a debian linux
>> machine (Pentium 166, 192M RAM) ... So something weird is happening on
some FreeBSD
>machines.>
>> But I also have two machines that are _dedicated_ mysql servers of the
same configuration,
>but other
>> hardware brand (motherboard, scsi controllers, disks) that runs perfect
on the
>same FreeBSD release!>
>> The machine with the problem were also running Apache/PHP .. >
>> (How )is MySQL using sharedmemory segments ? I know that Oracle takes up
loads
>of them and may> bring problem for apache that also needs some seg's.. ?> >
>> Regards,> Johan Andersson> Consultant QbranchHi!
>Can anyone of you guys come with a repeatable test case that will
>always lead to the situation as described. Then we could try to fixit.Regards,
>Sinisa
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php