strange behaviour when adding location

«

Previous topic

|

|

Next topic

»

Author	Message
Marko Žmak	Wednesday 15 February 2006 8:21:23 am I have a serious problem with adding new locations to objects in eZ. It generates a huge amount of SQL queries and overloads the server, the script crashes. The problem is described here: http://ez.no/community/forum/setup_design/strange_behaviour_with_adding_location -- Nothing is impossible. Not if you can imagine it! Hubert Farnsworth
Marko Žmak	Thursday 16 February 2006 7:59:12 am Does anyone know any sollution about this? Adding locations to objects is crucial for my site, so my site is uselles without it. Please help! -- Nothing is impossible. Not if you can imagine it! Hubert Farnsworth
Juan Pablo Vercesi	Thursday 16 February 2006 8:35:58 am Could you tell what are the queries about? Maybe that way it's possible to find out what's going on. Have you customized ez code? JP, may the source be with you.
Paul Borgermans	Thursday 16 February 2006 10:31:47 am Hi Marko, I tried this on a similar system (ezp 3.7.3, php 4.4). Adding many locations is indeed a CPU and query intensive process (here 1.8 secs for adding 4 locations at the same time, 102 SQL queries, all caches off, template compiling off, .... but its a fast machine ... has to be with ez publish). Try increasing the memory limit for php --paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans
Marko Žmak	Friday 17 February 2006 6:25:42 am No, i didn't customize eZ code. The machine I'm hosting my pages is Dual Xeon2.4Ghz. The execution od mysql queries lasts 6 seconds for adding 4 locations on this machine. I'll do some more testing and send the queries here on the forum. I also tried increasing php memory limit but it didn't help. And even if I increase it more and the script stops to crash, this doesn't solve my problem, since adding object to several locations at once is a crucial part of the user interface of my site. Maybe I'm just naive, but I don't see a reason why so many queries are needed for adding several locations at once. I bet it can be optimized. -- Nothing is impossible. Not if you can imagine it! Hubert Farnsworth

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

Main resources:

Total runtime	0.0123 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.0046	588.2500	151.2266
Module start 'layout'	0.0046	0.0019	739.4766	36.6641
Module start 'content'	0.0065	0.0042	776.1406	94.0469
Module end 'content'	0.0107	0.0015	870.1875	37.9922
Script end	0.0122		908.1797

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0020	16.3949	14	0.0001
Check MTime	0.0009	7.4181	14	0.0001
Mysql Total
Database connection	0.0008	6.6680	1	0.0008
Mysqli_queries	0.0020	16.6067	3	0.0007
Looping result	0.0000	0.0739	1	0.0000
Template Total	0.0011	8.9	1	0.0011
Template load	0.0009	7.1324	1	0.0009
Template processing	0.0002	1.7122	1	0.0002
Override
Cache load	0.0006	4.8100	1	0.0006
General
dbfile	0.0009	6.9381	8	0.0001
String conversion	0.0000	0.0389	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