I intend to do both (Improve Performance + Warn of XOOPS Slowness)

There is simply no getting around it, XOOPS isnt that fast.
Prove me wrong?
Stick a page gen time on xoops.org!

Also, I have no intention of bad mouthing XOOPS. Its a great software, just not fast.

I'm really frustrated with the speed of xoops, the features are ok, not the most featureful, but that would make it even slower.
I just think the dev team/you dont take this seriously. You've been telling me you 1 server to run a XOOPS site in order for it to be fast. Thats not reasonable.

To the dev team: I really do hope that you guys would work on code improvements that speed up XOOPS and maybe moving away from Smarty. Smarty is powerful and due to that, its somewhat slow. Maybe its a little too powerful? XOOPS needs a way to dramatically reduce its MySQL usage as well. All those queries take time. Anything to speed it up would be great...

Ok, so you are frustrated. Instead of expending that energy into something negative (like an article telling people how slow XOOPS is would be), turn it into somethng positive. Don't take this the wrong way, but you seem VERY comfortable with the idea of throwing in a few frustrated comments of where you think the problem is here and there, and then stand back with the expectation for others to fix it for you. I can tell you right now this is not the way Xoops, or ANY open source project works. A community driven project relies on community involement, and that means everyone, including you.

I'm just a standard XOOPS user, just as you are, and I feel I have put in considerable effort in trying to help you. With that in mind it baffles me as to why you are of the opinion that nobody (in partiular myself) takes you seriously. Did you expect someone to recode the entire XOOPS templating system and core for you in a couple of weeks just because YOU are having problems with sluggish performance on your site? I really don't understand the angle you are coming from, but from where I stand after the help I have personally given you it seems quite unrealistic and unreasonable.

The XOOPS template/caching system is not the best, and I don't beleive you'll find anyone who would claim it is. It also is not nearly as bad as you are making it out to be. From what I've seen of your site I would suggest that the majority of your sites performance problem sites squarely on the shoulders of your host. Along with my sites I also run a site with a mate called http://www.iis-resources. This site is hosted on an standard single AMD XP CPU based system along with half a dozen other sites, and has a great deal more content than yours. THis is the page exection time and MySQL counter from the main page - 0.301 Seconds | 142 Queries.

Quote:

Sheesh! Who let the frakking troll in?

ewonline, Members of this community have gone out of their way to be kind and respond in detail to your problems and also do so when yo started your childish whining.

My advice to you: get lost and grow up. If you don't like XOOPS then I recommend you go for PHP-Nuke and go whine on their forums.

I am going to draft this thread into an FAQ article on "How to optimise XOOPS perforamance" If any other comments or clarifications are needed in this thread, please add in.

Brash, maybe you already have something? No point in reinventing the wheel

Thanks , Richard

I am going to draft this thread into an FAQ article on "How to optimise XOOPS perforamance" If any other comments or clarifications are needed in this thread, please add in.

Brash, maybe you already have something? No point in reinventing the wheel

Thanks , Richard

I am going to draft this thread into an FAQ article on "How to optimise XOOPS perforamance" If any other comments or clarifications are needed in this thread, please add in.

Brash, maybe you already have something? No point in reinventing the wheel

[EDIT:] Hate to say this , but This double post is an example of what we have just been discussing.

Thanks , Richard

Carnuke, check your PM

the slowness of xoops,org is NOT due to the XOOPS system or the number of queries generated by the system (or it's template engine, for that matter), but because the server gets abused by ignorant and malicious peple a lot (people trying to download xoops.org all at once, bots harvesting e-mails from the wiki, adding porn links etc.). The wiki will be closed down soon, so that should increase the available resources.

Just thought I'd help you out of a fantasy I agree XOOPS (the system) can use some optimisations here and there, but generally speaking it's one of the fastest and most stable PHP/MySQL systems there is. If you don't want database queries, there are perfectly suitable alternatives (use XHTML and Dreamweaver to manage your site, for instance). XOOPS isn't built like that, so expect some slowdown due to database queries. Shared servers tend to allocate relatively small amounts of internal bandwidth to their shared sites (so one site cannot bring the server down), depending on your wishes, another host mightalso be an option.

Herko

Look Herko,

I have never once said XOOPS isnt one of the fastest CMS.
Its on the top 10 list of php CMS for sure.
No doubt about it.
I am simply trying to suggest that you make a effort to try and improve the performance of XOOPS perhaps by code revisions, betting caching, etc...

And McNAZ
Quote:

Take that and turn it around.