My site has been going down, and bringing others on my shared server down with it this week. My host told me that my FeedAPI module was creating pretty massive queries that were bringing the server as a whole to a crawl. I was pulling in a rather prolific Twitter feed at a rate of about 15 posts per minute at one point while testing, so that probably is to blame. I also had a couple word filters in the views page if that makes any difference. Either way, my host mentioned that FeedAPI can have that effect though even without the kind of high-volume feed I was pulling. He mentioned that pathauto can be quite consuming as well in conjunction with creating nodes from feeds, and could have played a part during the node creation stage. In any event, he advised me to be very cautious of using FeedAPI as these things can happen.
On the other hand, I really like this module and see nothing else I could use in Drupal to do the same thing. Anyone have advice on how I can configure or otherwise keep using FeedAPI to pull in feeds, sometimes rather high-volume and high-frequency ones, and at the same time keep the MySQL queries in line?
Comments
Comment #1
voipfc commentedThis is not the first time Drupal has been known to create demanding queries.
If you need a high level of performance you should consider a VPS.
Which host is it, anyway?
Comment #2
fumbling commentedRight, point taken. Yep, I'm moving to a VPS (albeit a small one for now). Nonetheless, anything I should keep in mind in terms of the number of posts per refresh, or the frequency of the refresh, or the node processor I use, settings, order of operations, etc? I'm sure I'm doing something somewhere that's not optimal and contributing to the issue.
Comment #3
aron novakdrupalot: Do you have some logs about (or ask the hosting company) about problematic queries? MySQL has such a feature to log the problematic queries. I'd happily optimize such queries if possible.
Comment #4
fumbling commentedThanks. After moving to the VPS, the problem seems to have mellowed or gone away altogether. At the very least, it's not hanging the server or any pages anymore. Regarding tracking the problematic queries, do you know where I'd navigate to the feature in PHPMyAdmin, assuming its there?
Comment #5
voipfc commentedInstalling the http://drupal.org/project/devel module will help you track your queries.
Enabling the slow query log in mysql.cnf should also help.
Comment #6
fumbling commentedThanks, I'll give it a shot.
Comment #7
alex_b commentedClosing after an extended period of inactivity.