Hello
Found the culprit and an ugly workaround.
The cronjob does not scale to bigger sites.
It starts linkchecking and this process is slow, because each link must connect or time out.
At my site, each instance of linkcheck use almost 6 hours to complete.
As each instance is already a resource hog on its own, 6 instances running simultaneausly exhausts system resources.
I had to reconfigure cronjob from hourly to at each 6 hours...
The rss export import are now very bad. Workflow....
A more reasonable solution could be using independent link check cron job from the other tasks.
The link check could run once a day.
Other solution could be check many links in parallel mode.
Regards. Andre Felipe
---
A Debian user never dies. Issues a last command:
shutdown -h now
Checking all links will always be a heavy operation for the system. It's not recommended to run it as part of the normal cronjobs. Use the cronjob-part to run the linkcheck as separate process : http://ez.no/products/ez_publish_cms/documentation/installation/the_cronjob_script
Kåre Høvik
You must be logged in to post messages in this topic!
