Uploading images via WebDAV = wasting harddisc space?

Next topic

Author	Message
Marco Zinn	Saturday 30 October 2004 10:18:35 am Hi, a long time ago, i posted a bug report (see http://ez.no/community/bug_reports/images_remain_in_images_versioned), because i think, there is a bug with image publishing: Files stay in images-versioned, even, after the image object is published. I think "images-versioned" does not get cleaned of unneed files. Now comes WebDAV: The folder /var/webdav/tmp get filled up with load of eZWebDAVUpload_xxxxx files, which don't seems to get removed. I have a customer, who's using Webdav to upload images. The images are published immediatly (by WebDAV) and probably, 98% of them are never edited. Now, this is the current harddisc usage: var/corporate/storage/image is about 14MB large var/corporate/storage/images-versioned is about 12MB large var/corporate/storage/original is almost 0 (36kb) var/webdav/root is 0 var/webdav/tmp is 67 MB large !!!! I'm using ez 3.4.2 with Webdrive beeing the WebDAV client. Please, someone tell me, how this SHOULD work, and if i can delete the var/webdav/tmp dir! Shouldn't the WebDAV server part of ez _move_ the files from the webdav/tmp dir to somewhere in var/storage ? Why is so much data in images-versioned, when we don't have loads of drafts? Also refer to my bug report, as i think, there are 2 problems: One with a bad cleanup of files in images-versioned (see report) and one with the webdav's tmp dir. Any comment? Is this a know bug? Marco http://www.hyperroad-design.com
Marco Zinn	Sunday 03 April 2005 6:57:36 am Hi, i'm kind of bumping this. We do have some ez 3.4 installations (3.4.4 or so), which make heavy use of image galleries. Because of 2 bugs (i think, these ARE bugs), the harddisc usage is very huge: Webdav does not delete it's temp files (this is fixed in 3.5, but still open in 3.4). Additionally, ez makes copies of (original) images files at every new version of the image object. And, as noone closed my bug reports, i'm almost sure, that ez also does not remove image files for deleted object versions. See these bug reports. http://ez.no/community/bugs/images_remain_in_images_versioned http://ez.no/community/bugs/no_cleanup_for_image_attributes So, my question to the users here: Does anyone use ez 3.4 for image galleries (with of without WebDAV) and has fixed these issues? To the ezCrew: At least the WebDav tmp file issue is solved in 3.5 . Will you backport this eo ez 3.4? Maybe this has already been done, but we're using 3.4.4, rev. 9297, and this still has this bug. Marco http://www.hyperroad-design.com

Author

Message

Saturday 30 October 2004 10:18:35 am

Hi,
a long time ago, i posted a bug report (see http://ez.no/community/bug_reports/images_remain_in_images_versioned), because i think, there is a bug with image publishing: Files stay in images-versioned, even, after the image object is published.
I think "images-versioned" does not get cleaned of unneed files.

Now comes WebDAV: The folder /var/webdav/tmp get filled up with load of eZWebDAVUpload_xxxxx files, which don't seems to get removed.

I have a customer, who's using Webdav to upload images. The images are published immediatly (by WebDAV) and probably, 98% of them are never edited.

Now, this is the current harddisc usage:
var/corporate/storage/image is about 14MB large
var/corporate/storage/images-versioned is about 12MB large
var/corporate/storage/original is almost 0 (36kb)
var/webdav/root is 0
var/webdav/tmp is 67 MB large !!!!

I'm using ez 3.4.2 with Webdrive beeing the WebDAV client.

Please, someone tell me, how this SHOULD work, and if i can delete the var/webdav/tmp dir!

Shouldn't the WebDAV server part of ez _move_ the files from the webdav/tmp dir to somewhere in var/storage ?
Why is so much data in images-versioned, when we don't have loads of drafts?
Also refer to my bug report, as i think, there are 2 problems: One with a bad cleanup of files in images-versioned (see report) and one with the webdav's tmp dir.

Any comment? Is this a know bug?

Marco
http://www.hyperroad-design.com

Marco Zinn

Sunday 03 April 2005 6:57:36 am

Hi,
i'm kind of bumping this. We do have some ez 3.4 installations (3.4.4 or so), which make heavy use of image galleries.

Because of 2 bugs (i think, these ARE bugs), the harddisc usage is very huge: Webdav does not delete it's temp files (this is fixed in 3.5, but still open in 3.4).
Additionally, ez makes copies of (original) images files at every new version of the image object. And, as noone closed my bug reports, i'm almost sure, that ez also does not remove image files for deleted object versions.

See these bug reports.
http://ez.no/community/bugs/images_remain_in_images_versioned
http://ez.no/community/bugs/no_cleanup_for_image_attributes

So, my question to the users here: Does anyone use ez 3.4 for image galleries (with of without WebDAV) and has fixed these issues?

To the ezCrew: At least the WebDav tmp file issue is solved in 3.5 . Will you backport this eo ez 3.4? Maybe this has already been done, but we're using 3.4.4, rev. 9297, and this still has this bug.

Marco
http://www.hyperroad-design.com

eZ debug

Timing:	Jan 19 2025 00:22:15
Script start
Timing:	Jan 19 2025 00:22:15
Module start 'layout'
Timing:	Jan 19 2025 00:22:15
Module start 'content'
Timing:	Jan 19 2025 00:22:16
Module end 'content'
Timing:	Jan 19 2025 00:22:16
Script end

Main resources:

Total runtime	1.0315 sec
Peak memory usage	4,096.0000 KB
Database Queries	52

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0068	588.0469	152.6406
Module start 'layout'	0.0068	0.0044	740.6875	39.4922
Module start 'content'	0.0113	1.0185	780.1797	497.9922
Module end 'content'	1.0297	0.0017	1,278.1719	12.1250
Script end	1.0314		1,290.2969

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0035	0.3432	16	0.0002
Check MTime	0.0014	0.1333	16	0.0001
Mysql Total
Database connection	0.0007	0.0683	1	0.0007
Mysqli_queries	0.9769	94.7144	52	0.0188
Looping result	0.0004	0.0430	50	0.0000
Template Total	0.9934	96.3	2	0.4967
Template load	0.0021	0.2074	2	0.0011
Template processing	0.9912	96.1003	2	0.4956
Template load and register function	0.0001	0.0099	1	0.0001
states
state_id_array	0.0009	0.0870	1	0.0009
state_identifier_array	0.0015	0.1442	2	0.0007
Override
Cache load	0.0018	0.1704	32	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0007	0.0635	1	0.0007
Fetch class attribute name	0.0010	0.1005	3	0.0003
XML
Image XML parsing	0.0004	0.0399	1	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0011	4	0.0000
General
dbfile	0.0008	0.0772	16	0.0000
String conversion	0.0000	0.0012	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
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
2	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
6	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
6	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 18 Number of unique templates used: 6

Time used to render debug report: 0.0002 secs