Loose memory with adodb
Re: Loose memory with adodb
yes, but me and somebody else here like to speek to you, it's better find speeder algorithm to generating menu, against thinking about little bites of memmory ...when theses informations are not right(probably, and not your fault).
Re: Loose memory with adodb
Oh no little - 3 - 4 MB !!!! I think you don't know of what we here are speaking.about little bites of memmory
Last edited by Piratos on Mon Dec 12, 2005 2:06 pm, edited 1 time in total.
Re: Loose memory with adodb
using xdebug and kcachegrind I got the following results (see attached picture)
It seems obvious where the bottleneck lies.
(this callgraph is 'sorted' bij time)
[attachment deleted by admin]
It seems obvious where the bottleneck lies.
(this callgraph is 'sorted' bij time)
[attachment deleted by admin]
Last edited by petert on Mon Dec 12, 2005 7:33 pm, edited 1 time in total.
Mambo sucks, that's why I am here.
Now they call it Joomla, but it still sucks!
CMSMS rules!
Now they call it Joomla, but it still sucks!
CMSMS rules!
Re: Loose memory with adodb
That's really interesting petert !
How exactly did you manage to get that graph ? Is there such a tool available for Windows ? My linux box does not have any X manager, so could this work without KDE ?
How exactly did you manage to get that graph ? Is there such a tool available for Windows ? My linux box does not have any X manager, so could this work without KDE ?
Re: Loose memory with adodb
'using xdebug and kcachegrind'melix wrote: How exactly did you manage to get that graph ?
http://www.google.nl/search?q=xdebug+kc ... :officialmelix wrote: Is there such a tool available for Windows ?
Read up on xdebug please.melix wrote: My linux box does not have any X manager, so could this work without KDE ?
XDebug is a debugger and profiler, the output of the profiler is fed into a program like kcachegrind. XDebug runs at the server and needs no X at all.
Mambo sucks, that's why I am here.
Now they call it Joomla, but it still sucks!
CMSMS rules!
Now they call it Joomla, but it still sucks!
CMSMS rules!
Re: Loose memory with adodb
I don't think kcachegrind will work without X, but thanks for your help 

Re: Loose memory with adodb
You are right about that, but where did I say it would?melix wrote: I don't think kcachegrind will work without X, but thanks for your help![]()
I thought you had to use windows cr.p for a gui program, that's the google link.
Mambo sucks, that's why I am here.
Now they call it Joomla, but it still sucks!
CMSMS rules!
Now they call it Joomla, but it still sucks!
CMSMS rules!
Re: Loose memory with adodb
Please look at http://sourceforge.net/projects/wincachegrind/melix wrote: I don't think kcachegrind will work without X, but thanks for your help![]()
Re: Loose memory with adodb
Thanks, seems to be what I was looking forcyberman wrote:Please look at http://sourceforge.net/projects/wincachegrind/melix wrote: I don't think kcachegrind will work without X, but thanks for your help![]()

Re: Loose memory with adodb
Problem with profiler classes is that you have to change your scripts. Those classes alter the behaviour of your scripts and slow them down and have nasty side-effects.maxi2 wrote: Here are two of the best profiler classes:
The XDebug route is transparent and in combination with kcachegrind it will allow you to emulate a 'run' of the program.
It uses the processor emulation of Valgrind to run the executable, and catches all memory accesses for the trace. The user program does not need to be recompiled; it can use shared libraries and plugins, and the profile measuring doesn't influence the trace results. The trace includes the number of instruction/data memory accesses and 1st/2nd level cache misses, and relates it to source lines and functions of the run program.
Mambo sucks, that's why I am here.
Now they call it Joomla, but it still sucks!
CMSMS rules!
Now they call it Joomla, but it still sucks!
CMSMS rules!
Re: Loose memory with adodb
it's mentioned on the very first hit of the google linkmelix wrote:Thanks, seems to be what I was looking forcyberman wrote:Please look at http://sourceforge.net/projects/wincachegrind/melix wrote: I don't think kcachegrind will work without X, but thanks for your help![]()
![]()
Mambo sucks, that's why I am here.
Now they call it Joomla, but it still sucks!
CMSMS rules!
Now they call it Joomla, but it still sucks!
CMSMS rules!
Re: Loose memory with adodb
Don't be upset : I've been working both very hard and late to hunt those PHP4 vs PHP5 reference management differences, and it's been quite stressing 

Re: Loose memory with adodb
I am not upset, just disapointedmelix wrote: Don't be upset : I've been working both very hard and late to hunt those PHP4 vs PHP5 reference management differences, and it's been quite stressing![]()

(get some rest, will do you good)
Mambo sucks, that's why I am here.
Now they call it Joomla, but it still sucks!
CMSMS rules!
Now they call it Joomla, but it still sucks!
CMSMS rules!
Re: Loose memory with adodb
So don't be disapointed : you managed to get me right to xdebug
Well, I don't think it's a good idea to have software named xsomething if it doesn't require X, but that's how the X goes 


Re: Loose memory with adodb
In my daily computer hour in my hollyday i play something with phpedit and his debugger.
The questions - what happens if i load the default page with a fresh installed 0.11
All Smarty plugins are registered (plugins there are never used too)
All Smarty Informations are stored 9 times !!
All informations of the complete tables content and content_props are stored in Object(CmsObject) contentcache
All datas of the modules are stored (plugins there are never used too)
Many datas of the logger are stored , but no user need it.
You loose a lot of memory and time.
The questions - what happens if i load the default page with a fresh installed 0.11
All Smarty plugins are registered (plugins there are never used too)
All Smarty Informations are stored 9 times !!
All informations of the complete tables content and content_props are stored in Object(CmsObject) contentcache
All datas of the modules are stored (plugins there are never used too)
Many datas of the logger are stored , but no user need it.
You loose a lot of memory and time.