pubsvn troubles today

«

Previous topic

|

|

Next topic

»

Author	Message
Paul Borgermans	Tuesday 14 September 2004 6:08:19 am sorry for those who suffered difficulties on pubsvn today, search robots and websvn access caused an extra load of ~60GB on /tmp that in turn made updates from the master repository impossible -paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans
Björn Dieding@xrow.de	Thursday 16 September 2004 10:24:15 am What do you mean my load? Traffic, Diskspace or else? I am just curious... Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs Looking for hosting? http://hostingezpublish.com ----------------------------------------------------------------------------- GMT +01:00 Hannover, Germany Web: http://www.xrow.com/
Paul Borgermans	Thursday 16 September 2004 11:35:39 am You are so curious ;-) It was mainly a disk space problem: when updating from zev.ez.no, the update script needs temporarily around 2.6 GB for sanity checking and correction ... websvn had generated a cache by the action of search robots and left a few hundred MB on the volume holding pubsvn. That means a complete directory with all ezp files for every revision + tar balls for all directories. Hence the 60GB :-) Furtunately, bandwidth is not a problem here. Cheers -paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans
Björn Dieding@xrow.de	Thursday 16 September 2004 2:04:48 pm I just had this idea about the robots.txt I noticed you have it already :-) <thumb up> http://pubsvn.ez.no/robots.txt Did you created it just lately? Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs Looking for hosting? http://hostingezpublish.com ----------------------------------------------------------------------------- GMT +01:00 Hannover, Germany Web: http://www.xrow.com/
Paul Borgermans	Thursday 16 September 2004 3:01:07 pm No, it was there a long time, but the rule for websvn was missing I first thought is was a good idea to let the spiders fill the cache, now I don't think that anymore :-) cya -paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans

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 19 2025 10:01:57
Script start
Timing:	Jan 19 2025 10:01:57
Module start 'layout'
Timing:	Jan 19 2025 10:01:57
Module start 'content'
Timing:	Jan 19 2025 10:01:57
Module end 'content'
Timing:	Jan 19 2025 10:01:57
Script end

Main resources:

Total runtime	0.0195 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.0061	590.2656	152.6094
Module start 'layout'	0.0061	0.0038	742.8750	39.4141
Module start 'content'	0.0099	0.0076	782.2891	93.3047
Module end 'content'	0.0174	0.0021	875.5938	38.3047
Script end	0.0195		913.8984

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0028	14.4406	14	0.0002
Check MTime	0.0011	5.7328	14	0.0001
Mysql Total
Database connection	0.0012	6.0367	1	0.0012
Mysqli_queries	0.0032	16.2827	3	0.0011
Looping result	0.0000	0.0830	1	0.0000
Template Total	0.0016	8.3	1	0.0016
Template load	0.0009	4.5938	1	0.0009
Template processing	0.0007	3.6867	1	0.0007
Override
Cache load	0.0006	3.2827	1	0.0006
General
dbfile	0.0035	17.7660	8	0.0004
String conversion	0.0000	0.0391	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.0001 secs