Deprecated - Performance and scalability

Hi all,

I am trying to build a news aggregation service much like newsnow.co.uk - however I run into problems with cron timeouts when using the build in aggregator module. When having added around 100 feeds the crons simply take too long. This is kind of a big problem since I was hoping to add several thousands of RSS feeds to the aggregator... Anyone have any suggestions?

Thanks!

this is guru,
i want to know how to add a text box in administer(menu)-> users ->add users .....page.there already three boxes r available i want to add one more text box - for my drupal site what should i do......

I'm looking into slow results from a search and it seems that the most time is spent in search_excerpt(). In particular, the line: if (preg_match('/'. $boundary . $key . $boundary .'/iu', $text, $match, PREG_OFFSET_CAPTURE, $included[$key])). I'm not sure I understand the need for $boundry. Removing it makes the search much faster.

What's the reason for it? If the search key is known to be in $text, why not search for just the key?

Over the past several weeks, I've noticed a steady increase in page load times. I use the site extensively throughout the day and recently it's been pretty rough.

Please note that I am not bitching, but speaking as someone who's agonized in the past with performance tweaks on high traffic Drupal sites, I'm very interested in the understanding the resources involved in keeping a beast like this site up and running as well as how often these resources are outgrown, etc.

The 4.7.3 aggregator at http://liquidvisual.ca/visitors/en/aggregator/sources

happily updates many feeds, but not

http://ocw.mit.edu/OcwWeb/rss/new/mit-newcourses-av.xml

and many others:

Updating the items on the admin aggregator pages does nothing. The log indicates that there are items to update, but they are not added to the database and do not appear as items.

The main News Feed from http://www.hrw.org/cgi-bin/rss.cgi?t=news_rss produces the following warnings:

* warning: xml_set_element_handler(): supplied argument is not a valid XML Parser resource in /modules/aggregator.module on line 814.
* warning: xml_set_character_data_handler(): supplied argument is not a valid XML Parser resource in (path removed) /modules/aggregator.module on line 815.
* warning: xml_parse(): supplied argument is not a valid XML Parser resource in (path removed) /modules/aggregator.module on line 817.
* warning: xml_get_error_code(): supplied argument is not a valid XML Parser resource in (path removed) /modules/aggregator.module on line 818.
* warning: xml_get_current_line_number(): supplied argument is not a valid XML Parser resource in (path removed) /modules/aggregator.module on line 818.
* warning: xml_get_error_code(): supplied argument is not a valid XML Parser resource in (path removed) /visitors/modules/aggregator.module on line 819.

I've been having issues with server overloads on a very low-volume Drupal site. My hosting company has suggest that the php scripts that are running are overloading the CPU. One of the suggestions they've made is to:

"Make the main drop page people go to on the site static so they have to enter from the site to a php page. Getting dropped into a php page uses extra load since it's resolving the initial domains dns while running the page. "