{"id":316,"date":"2008-04-12T11:10:02","date_gmt":"2008-04-12T16:10:02","guid":{"rendered":"http:\/\/unitstep.net\/?p=316"},"modified":"2008-04-12T11:10:36","modified_gmt":"2008-04-12T16:10:36","slug":"threatfire-hanging-or-slowing-down-mysql","status":"publish","type":"post","link":"https:\/\/unitstep.net\/blog\/2008\/04\/12\/threatfire-hanging-or-slowing-down-mysql\/","title":{"rendered":"ThreatFire hanging or slowing down MySQL?"},"content":{"rendered":"

\"XAMPP<\/p>\n

After seeing glowing<\/a> recommendations<\/a> for the heuristic-based ThreatFire<\/a> anti-malware app from PC Tools, I decided to install it to complement my antivirus scanner and other anti-spyware tools such as Spybot-S&D<\/a> and Ad-Aware<\/a>.<\/p>\n

Initially, it worked fine. While I don’t know how much protection it really added, it was intuitive, easy to configure and didn’t slow down my system like many other real-time scanners might have. However, I ran into some trouble with my web development environment, consisting of Apache, MySQL and PHP<\/acronym> (in the form of XAMPP<\/a>) that I could only attribute to ThreatFire’s presence.<\/p>\n

<\/p>\n

The symptoms<\/h3>\n

With ThreatFire installed and enabled, requesting any pages from Apache that would result in MySQL access took painfully long. Accessing static pages or scripts that did not use the MySQL database did not hang. At first, I thought it was a problem with the application\/scripts I was working on, but other popular third-party scripts, such as phpMyAdmin<\/a>, were also slow or unresponsive. The server appeared to “hang” for about 10-15 seconds before producing any response. This was on a local server.<\/p>\n

I tried several different courses of action, such as:<\/p>\n