Loading...
 
Skip to main content

Development


Why does it need 243 database queries and 2.43 seconds to render this page ?

posts: 10

NASTY_RANT

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 😊

/NASTY_RANT

posts: 10

Also, could someone explain this fetish for blocks that PHPNuke/PostNuke/Tiki users have.

It seems developers have this fetish side blocks, which really annoies me. Do we need all that information thrown into our face all at once ? I'm sure we dont as it's on every page. Users are overwhlemed with information, which only scares people from using the site

Runs away in fear caused by information overload
posts: 2881 United Kingdom

Remove them! they are optional through Admin->Modules!!

Damian


posts: 1001 Canada

Hi ))MehMehMeh((,
you can remove modules, checkthe link at top (in moreneat). If you're talking about default ones on tw.o, you can talk to admins here about it on the IRC channel, or open something in the tracker about the site although it's pretty much unmaintained 😊

About the rest, maybe some places are more appropriate for announcing your intention to start a new CMS. I'm not a coder and I don't know much about other CMSs but maybe you're right thinking that only you realized the truth yet about CMS-programming.

If you can point me to where you red the mathematical demonstration of 243 being the minimum queries number needed, I'll be glad to fix that. If you finally get this infinite time and concentration, be sure to help us, we could badly use it 😁

If I can talk for a part of the community, I know me and Chealer9 aren't going to help in a new CMS's development, but I will without fault as soon as you post back that the magic vision you have can do as much as Tiki in 242 queries. But I'm wondering what will come first : the removal of your post by Tiki admins trying to lure our users or your announcement about beating Tiki 😐

Good luck


posts: 10

Well, yes I know you can remove modules, like you can in PostNuke or any other similar CMS.

However my point is it should not take 200-250quieres to show the blocks and module content of this page ! Just look at the fotter of this page and see that. A page with all the blocks like thins should not take >40 queries at the most if it was properly programmed. If someone can justify why all these queries are needed, I would be happy, however I know that no one will, because there is ***no way*** they can be justified, because once someone explains what each query did, they'd probably soon realise that many of these queries can be removed. As may realise, the 243 does vary a little between 200-250, so there is no hard and fast formula. However it doesn't take a genius to realise that it's just not right to use all those queries, it just make the CMS slow and bulky.

I'm not the only person who has realised that Open Source PHP CMS's atm are poop in general. There are many other developers on Sourceforge who I have contacted who think the same.

I certainly will prove that something similar can be done with less queries, given a bit of time. Personally given infinite time and concentration, I'd rather work on a new CMS project with a few developers who know what they are doing than try and clean up a CMS like this, as Tiki is just far too badly designed to allow for it to be cleaned up without a major reworking of it's code at every level. It's a shame really because Tiki does have a huge number of modules, and it's ideal of being able to be a feature rich CMS is a great idea. However somewhere along the line, the lack of strategy, planning and evaluation has made Tiki a messy project that follows in the foot steps of the *Nukes, which is a shame.

Fair enough I was luring people away from tiki if they were to help work on another CMS, however, I doubt it would make much difference because I doubt there will be enough talented coders reading this post that would email. If tiki admins are against the idea of that, they can edit my post so the bit is omitted. However if they delete the post, it will only mean they just simply don't give a damn about working on a system that is efficient, and just makes them ignorant by ignoring what their target audience/users have to say. Sure enough it will happen. However, if they edit out the post and listen to the rest of what I am saying, maybe they will think twice and make an effort to work on producing much better code. This project has nearly 400 developers working for it. I'm sure if a a bunch the better coder came up with a new design strategy and assigned the task of coding it to all the other developers, I'm very certain, with in a few weeks, they could make something a lot faster, cleaner and more futureproof (i.e. using good OOP design to make code reuseable, smaller etc). I have good set of ideas in my brain I am putting to UML for a CMS that would produce something as functional as Tiki but at the same time faster and probably EVEN MORE flexible/powerful.

As for the blocks. I'm sure removing some on this site will speed it up, and may contribute a little to reducing the silly number of queries on the database. The blocks are repeated on every page, and once you've seen them once it's just a waste of time, and bandwidth displaying them on every page as clutter.


posts: 2

Wow.
I think you're complaining way too much. Quite possibly Tiki is not 100% efficient. Or even 50% efficient. Why don't you check out the cvs version and see if you can help speed it up. Instead you produce a long rant. Vision changes, new ideas come up and software becomes better (hopefully).

This is open source, you're free to use it, or not. Up to you. But putting down someone's work is pretty low I think. There's a difference between constructive crtiricism and being an ass.


posts: 10

QUOTE
__

I think you're complaining way too much. Quite possibly Tiki is not 100% efficient. Or even 50% efficient. Why don't you check out the cvs version and see if you can help speed it up. Instead you produce a long rant. Vision changes, new ideas come up and software becomes better (hopefully).

_

Well, if it was just a code related issues, I would be more than happy to help out, and patch up things on the CVS. However, it seems to me that Tiki will never be efficient until they change the design of it. I'm not just talking about speed here, there are conceptual issues I disagree with here in the way it handles content. to me, if Tiki was be a great project as a piece of code as well as and end product for others to use, I think it's ***design*** needs changing.

I think this is the trouble with so much open source software, escpecially in thinks like this, PostNuke, and PHP Nuke. Each project has a really good vision for a good project, and they have coders capable of making this vision a reallity. However the bit in the middle, the design just seems to be lacking to me. I have my own idea of how a CMS/Portal should work, and I am working on it as a project myself. I'm still planning and designing it, and I don't want to dive into coding until I'm truely happy with the design and feel that everything is as efficient as possible.

Since upgrading this site to 1.8, there do seem to be a few less SQL queries, but it's still a lot of queries.

I'm not putting down someones work. I'm questioning the fact why there is so many queries and why the system is so resource intensive. OK, fair enough, I haven't been very polite about it, but it is the harsh reallity. I'm just saying if there was a bit more thought about the design of the product, Tiki would be a much better system, and won't be as limited as it is (for instance people can tell these days if Tiki or *nuke is used to make a page).

I know software is never going to be 100% effiecent, however Tiki is far too resource intensive.


posts: 6 Vanuatu

Remarks about the OP's long, whiney rant aside... Is anyone going to answer his question about why TikiWiki requires so much database overhead just to generate a page containing a forum thread?

posts: 2881 United Kingdom

Nope 😊

short answer: Its not optimised.

If its so worring for you, I suggest at this point in time, to install a phpBB and enjoy it.

Damian

posts: 6 Vanuatu

> If its so worring for you, I suggest at this point in time, to install
> a phpBB and enjoy it.

It doesn't worry me, I just think the OP's question was valid, even if his tone was a little rude (I don't think Tiki is a "turd"). By the same token, getting defensive when someone criticizes your work isn't productive, either.

posts: 2881 United Kingdom


Im not being defensive. If you look at the way tiki is written or rather has evolved over the many releases from the original it is indeed due for a optimisation session. However with so many CVS commitors around 250! it would be very hard to enform yet more coding standards and rules for database access.

Maybe in Tiki-2 it will be addressed, but thats a long long way away. We have Tiki 1.10 and 1.11 to code and release first.

Damian
Project Admin

posts: 6 Vanuatu

>...with so many CVS commitors around 250! it would be very hard
> to enform yet more coding standards and rules for database access.

I understand the logistics involved with a major restructuring. That's where the Project Admin steps in and starts waving his club around. 😀 When you're done with 1.x development (haha... I said "done" and "development" in the same sentence), consider accepting only submissions that directly affect the refactoring efforts.

posts: 2881 United Kingdom

LOL

Sorry but Project Admins in TikiWiki Community land are only here to recruit. The Community gets the say in what happens to the code not us.

TikiWiki project will always be wide open in terms of CVS access. Thats what makes the Community what is it. The spirit can really be felt in the IRC channel.

Damian


posts: 2881 United Kingdom

Remove them! they are optional through Admin->Modules!!

Damian


posts: 1
I would take a look at the Plone project before trying to start yet another CMS project.

posts: 71 United States

You're lucky. I'm using 643 database queries to load this page 😑

If you have any ideas of how to improve performance without jumping into Tiki version 3 or something, please let us know on the development mailing list.


posts: 175 Canada

Hey;

Just for fun I removed all the Modules from the layout. All I see is the log in and app menu.

Well gee guess what? Now I am getting 368 queries! WOW
With them I am getting 450 or so.
So although I was expecting this to help it made little difference.

But what can I say, TW still rules!

James

posts: 2881 United Kingdom

Forums are the worse culprits for queries. Especially if your site admin!

Damian