| malakajoe |
10-16-2004 01:35 PM |
Fix to GFY search problems
I was going to keep this to myself but I am in a good mood today.
For those using FreeBSD, you should already know their is an issue with MySQL CPU usage being high because of how FreeBSD handles threads. This just might be the issue with GFY.
http://dev.mysql.com/doc/mysql/en/FreeBSD.html
http://mysql.oss.eznetsols.org/books...rpts/ch06.html
Quote:
Alternatively, you can link MySQL on FreeBSD 4.x against the LinuxThreads library, which avoids a few of the problems that the native FreeBSD thread implementation has. For a very good comparison of LinuxThreads versus native threads, see Jeremy Zawodny's article FreeBSD or Linux for your MySQL Server? at http://jeremy.zawodny.com/blog/archives/000697.html.
|
Quote:
Another popular free operating system, FreeBSD, has threading problems that are much worse. Versions prior to 5.2 provide rather weak native threading. In some circumstances, I/O-intensive threads are able to get an unfair amount of CPU time, thus keeping other threads from executing as quickly as they should. Given the I/O-intensive nature of some database queries, this has a rather devastating affect on MySQL.
|
So I did my good deed for the day. I am going out now. Hopefully Adult.com and Jupiter will look into this and see if this is the issue with the search taking over the server response.
:glugglug |
