removeSubtrees - speed and memory

« 
Previous topic
|
Developer
|
Next topic
 »
Author Message

Fabien Mas

Tuesday 30 March 2010 8:58:00 am

Why eZContentObjectTreeNode::removeSubtrees is so low

and

why is it increasing memory so far ?

When I have more than 1000 objects to delete it takes hours when my memory limit is enought high

Is there a way to have better performances ?

Thx
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 30 2025 21:31:09
Script start
Timing: Jan 30 2025 21:31:09
Module start 'layout'
Timing: Jan 30 2025 21:31:09
Module start 'content'
Timing: Jan 30 2025 21:31:09
Module end 'content'
Timing: Jan 30 2025 21:31:09
Script end

Main resources:

Total runtime0.0213 sec
Peak memory usage6,144.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0050 588.1328151.2109
Module start 'layout' 0.00500.0030 739.3438220.6875
Module start 'content' 0.00800.0119 960.0313993.6016
Module end 'content' 0.01990.0014 1,953.632829.9922
Script end 0.0213  1,983.6250 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002411.1171140.0002
Check MTime0.00104.5193140.0001
Mysql Total
Database connection0.00083.840610.0008
Mysqli_queries0.00198.801530.0006
Looping result0.00000.042510.0000
Template Total0.00104.710.0010
Template load0.00083.727710.0008
Template processing0.00020.989510.0002
Override
Cache load0.00052.401610.0005
General
dbfile0.00146.421180.0002
String conversion0.00000.033540.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs