Re: Mysqld chewing up cpu in the background.
Thanks for the suggestion. That did help me find out. It wasn't idle. The problem is that its taking 10 seconds to insert a single record, composed mainly of one longtext field. The index is killing me. Does anyone know of how FT indexing can be changed to do inserts quicker or something? On 7/25/05, Richard Dale [EMAIL PROTECTED] wrote: I am fairly sure that there aren't any queries being run, but while in the background, my mysqld process chews up exactly 50% of my cpu. It runs queries nicely and has excellent response times for most any query I throw at it, but its causing issues for other apps. Try using mytop to see if there are queries going on. It's like the unix top command. http://jeremy.zawodny.com/mysql/mytop/ Also try: SHOW PROCESSLIST; If you use InnoDB: show innodb status; Best regards, Richard Dale. Norgate Investor Services - Premium quality Stock, Futures and Foreign Exchange Data for markets in Australia, Asia, Canada, Europe, UK USA - www.premiumdata.net -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Mysqld chewing up cpu in the background.
At 09:16 AM 7/27/2005, you wrote: Thanks for the suggestion. That did help me find out. It wasn't idle. The problem is that its taking 10 seconds to insert a single record, composed mainly of one longtext field. The index is killing me. Does anyone know of how FT indexing can be changed to do inserts quicker or something? You could try going back to the default word length of 4 or more. I suspect the common everyday words like the and are producing a lot of duplicate index entries. Mike -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Mysqld chewing up cpu in the background.
I am fairly sure that there aren't any queries being run, but while in the background, my mysqld process chews up exactly 50% of my cpu. It runs queries nicely and has excellent response times for most any query I throw at it, but its causing issues for other apps. Try using mytop to see if there are queries going on. It's like the unix top command. http://jeremy.zawodny.com/mysql/mytop/ Also try: SHOW PROCESSLIST; If you use InnoDB: show innodb status; Best regards, Richard Dale. Norgate Investor Services - Premium quality Stock, Futures and Foreign Exchange Data for markets in Australia, Asia, Canada, Europe, UK USA - www.premiumdata.net -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
