Why check URLs?

«

Previous topic

|

|

Next topic

»

Author	Message
James Packham	Tuesday 23 March 2004 2:09:43 am This isn't really related to any particular problem that I have, but why does the runcronjobs script check the validity of URLs in the database? It doesn't seem to do anything with the information and it makes the script take a lot longer to run. Regards, James
Bruce Morrison	Tuesday 23 March 2004 6:58:54 pm Hi James Links are marked invalid if they cannont be retrieved by the cron job. In the admin site go to "Setup" -> "URL management" and you will see a list of urls that appear in the content of the site (XML text and URL data types). You can click on the "invalid" tab to see links that the cron job had trouble accessing. I agree that if you are running runcronjobs.php on a regular basis then the checking of the links is overkill especially if there are a lot of them. It would be ideal if you could have the runcronjobs.php script run every 15 minutes but be able to define that the individual scripts are run say one a day or once a week. At the moment it an all or nothing proposition. Cheers Bruce My Blog: http://www.stuffandcontent.com/ Follow me on twitter: http://twitter.com/brucemorrison Consolidated eZ Publish Feed : http://friendfeed.com/rooms/ez-publish
James Packham	Monday 05 April 2004 5:27:30 am Sorry I took so long to get back. Yes it is definately overkill to check urls every 15 minutes!! It's ok at the moment, but what happens when I get a really huge database of links? I think I might have to investigate a bit, to see if I can get rid of this feature and put it in a different cron job (One that runs once a day perhaps). Thanks, James
Antoine W.	Tuesday 30 August 2005 2:37:13 am Hi, Do you think it's really needed to run runcronjobs.php every 15 minutes ? It takes more than 20 minutes to check every urls, so I cant run it so frequently... What can be wrong if I run the script only once a day ? Thanks

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing:	Jan 18 2025 19:20:20
Script start
Timing:	Jan 18 2025 19:20:20
Module start 'layout'
Timing:	Jan 18 2025 19:20:20
Module start 'content'
Timing:	Jan 18 2025 19:20:20
Module end 'content'
Timing:	Jan 18 2025 19:20:20
Script end

Main resources:

Total runtime	0.0177 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0053	587.7813	152.6094
Module start 'layout'	0.0053	0.0038	740.3906	39.3984
Module start 'content'	0.0090	0.0065	779.7891	93.2578
Module end 'content'	0.0155	0.0022	873.0469	34.3047
Script end	0.0177		907.3516

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0026	14.8051	14	0.0002
Check MTime	0.0012	6.8193	14	0.0001
Mysql Total
Database connection	0.0006	3.5886	1	0.0006
Mysqli_queries	0.0026	14.7647	3	0.0009
Looping result	0.0000	0.1130	1	0.0000
Template Total	0.0017	9.9	1	0.0017
Template load	0.0009	5.1306	1	0.0009
Template processing	0.0008	4.7081	1	0.0008
Override
Cache load	0.0006	3.4877	1	0.0006
General
dbfile	0.0003	1.4801	8	0.0000
String conversion	0.0000	0.0404	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0002 secs