Why does it need 243 database queries and 2.43 seconds to render this page ?
Please people tell me this ....
Why does it need 243 database queries and 2.43 seconds to render this page ?
Just Why ? Does a forum page need every single query ? I guess not. Invasion Board is not super efficient, but look that that, it takes about 5-12 queries for the average page. It can render it in about 0.05 seconds as well I know time is realavive to the CPU power, however, 2.43 seconds is slow even if it's on an old P3 system!
What does this link prove as well....
http://validator.w3.org/check/referer
???? To me it proves the fact the Tiki want to look good, yet they still use the same ID for several DIV tags.
I'm not suprised you need GZIP support. If you disabled it, this page would probably time out on my PSDN modem.
Sure, I might be wrong ( somehow though I think not :P ), but do all PHP CMS systems need to be as badly designed as they are. PostNuke, PHP Nuke and Tiki have more Spaghetti in their code than a Spaghetti factory. Some of the approaches to development make me cringe. I'm not just saying Tiki is slow and badly coded. I'm say the majority of CMS's are in PHP. It seems to me that developers just want to spin out code as quickly as possible to get half working project and a user base.
I've been web programming in HTML, CSS, SQL, JavaScript and PHP now for almost 2 years, and I'm sure there are many developers out there with the same vision as me of making a CMS/Portal/MVC framework that is fast, functional, easy to use and is well written. I know given infineate time and concentration I would easily be able to make something better than any of the rubbish out there. The only CMS with some half decent coding is Xaraya, and even still I disagree with their 'solution' to content management.
If anyone does feel the same way about CMS's maybe they would want email me at Jason -at- Hybd Dot Net. Given a bunch of other developers with the same vision as me, I hope that we prove this point that a system like this, that is well written does not need to take >2 seconds to render a simple page and use 170-250 queries for each page. I'm not against Tiki personally, I'm against the direction most Open Source CMS's are going. You only need to look at PHPNuke and PostNuke to see that bad coding has left these projects in the dark now with no recent updates.
I am in planning/alpha stages of developing a CMS, and I have a solid plan I will put into UML over the next few days. If any one would like to join this project, feel free to email me. I don't plan to be one of these stupid idiots who intend to start a decent project and not finish it, and given the support of some decent PHP developers, we can prove that there is another alternative !
And Tiki developers are so keen to support this project, please explain in detail what each of the 243 queries does towards generating this page, and tell exactly why that query is needed. I very much doubt any developer could give reasoning for this! The simple answer to that is because there is no reason to need to generate a page with 243 queries. Is it me or has the evaluation progress been accidentally omited from Tiki's development cycle ?
No doubt some administrator will remove this post in a vain attempt to hide the truth that Tiki is written like turd, and because developers can not accept that Tiki really needed to re think it's appraoch to development. However, I might be wrong, maybe someone can justify all 243 SQL queries. In that case I give credit to that person 😊