I made few tests on a collection view (in localhost).
test 1) 5000 items with JDOM fields. executions never completed with out of memory error.

test 2) 5000 items with simple ECHO output of the objects fields. page always rendered.

test 3) 100 items with JDOM fields. page rendered but 6 times slower than the simple ECHO output.

I like JDOM, but I'm also concern about performances, and on a busy website I'm not really sure I would use a component with JDOM. any suggestions, opinion to improve this is very welcome.
thanks in advance for your attention.

Yes you are right. Confort has always a price, this is the problem.

For huges lists, replace JDom with a raw echo and HTML tags manually formated. You can look at the generated source, and paste it in your layout, replacing the JDom call, and customising the dynamics vars.

I am pretty sure that you can know wich pages can return that quantity of items.

For sure JDom can also be improved on this point. (Using cache maybe)
Let say above 50 rows JDom is not the best, I recognize it. But don't worry, because you can absolutly replace it where you want, it will not affect the application layer. It only deal with the final rendering and loading assets. (don't forget them : JS, CSS)

I would add, in developpement use JDom because it is more easier to design and syntax, and when you are ready for production, you can optimize your critical calls.

thanks for the reply. I probably will do as you say.

it's not easy to remove completely Jdom from the component, it requires time.
Why couldn't Jdom be improved?
I understand it requires time to rewrite its logic and probably it's not planned at the moment, but I would put this task as a priority before anything else, it would be a very important improvement to the entire jcook project.

A good news is that I improved JDom yesterday for the coming 2.5.
It is much better now but I cannot upload because it is not completly compatible with your current component.

I mean the core is compatible, but some classes have moved place.

Actually JDom is very slow because of the lacking core. There in an horrible recursivity call inside. I say, really horrible code.

PS : I did'nt said to remove JDom completly, I only suggested for those call in critical huge lists only. When you have a pagination, no problem.


I can submit here dom.php and html.php, but I prefer to offer you the surprise of the new version.

Thank you very much for your quick reply! you saved me time and headache to remove JDOM.
Even if I like Jdom, I'm concerned about performances, I was planning to remove JDOM from my components.
I know the main problem is only on lists, but if you consider a busy website each little thing multiplied for each user become a big issue, and I'm concerned about that.
So for now I'll continue on my development without caring about Jdom performances, I'm really looking forward for the new Jdom release.
I'm also concerned about performances of Joomla itself, but hopefully reducing joomla to its basic framework, everything should work smooth, otherwise I couldn't understand how IKEA, EBAY, McDonalds, PAYPAL, etc. etc. would use joomla in their framework.
thanks again.

note:
I know those big companies don't use joomla as their main framework, but I know they use "something" of joomla in their systems

do you know (more or less) when the new Jcook 2.5 will be released?
I'm just trying to understand and plan my schedule.

Tomaselli wrote: ...otherwise I couldn't understand how IKEA, EBAY, McDonalds, PAYPAL, etc. etc. would use joomla in their framework.

I think the answer to that is dynamic server deployment: amazon EC2 and other alternate cloud-based server implementations

Well excited about the new Cook version 2.5!!!

@admin - do you have a clearer idea on a release?

Many thanks,

Gez