Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/20/d268022878/htdocs/forum/viewtopic.php on line 988

Strict Standards: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/20/d268022878/htdocs/forum/viewtopic.php on line 988
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4284: Cannot modify header information - headers already sent by (output started at /viewtopic.php:988)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4286: Cannot modify header information - headers already sent by (output started at /viewtopic.php:988)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4287: Cannot modify header information - headers already sent by (output started at /viewtopic.php:988)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4288: Cannot modify header information - headers already sent by (output started at /viewtopic.php:988)
FAROO Forum • View topic - Memory leak - Observations

Memory leak - Observations

Bug reports

Memory leak - Observations

Postby TomHH » Sat Feb 26, 2011 6:06 am

I tried to figure out some conditions under which the memory consumption increases over time.

1) Crawler-Queue is empty, Faroo only stores words from distributed index: No memory problems even after several days online time.

2) No crawler activity, but many words in cache to store to the distributed index: Memory consumption quickly raises, even though the number of words in cache is (nearly) unchanged.

I would think that the process of looking for suitable clients to store words may be a good starting point to find the cause for the memory leak.
What are your thoughts?

Regards,
TomHH
TomHH
 
Posts: 40
Joined: Sat Dec 18, 2010 5:37 am

Re: Memory leak - Observations

Postby Wolf » Sun Feb 27, 2011 2:47 pm

TomHH wrote:I tried to figure out some conditions under which the memory consumption increases over time.

1) Crawler-Queue is empty, Faroo only stores words from distributed index: No memory problems even after several days online time.

2) No crawler activity, but many words in cache to store to the distributed index: Memory consumption quickly raises, even though the number of words in cache is (nearly) unchanged.

I would think that the process of looking for suitable clients to store words may be a good starting point to find the cause for the memory leak.
What are your thoughts?

Regards,
TomHH

Thank you very much for the info. This is close to the results from our tests. Although the problems might be also caused by the URL monitor or by the crawler queue processing.
Wolf
Site Admin
 
Posts: 130
Joined: Wed Dec 17, 2008 12:28 pm


Return to Bugs

Who is online

Users browsing this forum: No registered users and 1 guest

cron