My Enviornment is as follows:

Windows 2003 Server / IIS 6.0
PHP Ver. 4.3.11
MySQL 4.1
XOOPS 2.0.13.1 (My First & Only Installation to date)
WordPress 2.02
Web Links .93
Cafepress 1.03

I have a few questions that I hope someone is willing to help clarify for me.

1. I am comfused about all the diffrent versions. I installed my version (2.0.13.1) becasue at the time it was recomended as the "most stable". However there seems to be a lot of people who are using the 2.2x versions.

What is the diffrence and should I upgrade to a 2.2x version or just go to 2.0.14?.

If I go to 2.0.14, I have not seen any specific instructions for that particular upgrade. All I see is the full version. Since I have already done a significant amount of customization to templates theams and have over 1000 links in my Web Links module, I am very hesitant to do much of anything. I also have no idea how the other modules may be effected.

2. Additionally ny site is taking a very long time to load an I am still in development so there is not realy traffic to speak of. My site is loaded on a dedicated server where I host other primarily small HTML sites for just my clients. So, that means I do not have an enormaous amount of traffic on the server nor do I have spammers etc.

Any Ideas on this? Is this inherent issue with XOOPS or are there things I can do to help speed up load time?

I have noticed similar perfomance issues on this site as well where the site itself can take forever to load and I have 1.5k broadband ISP connection and an P4 3.0 GHz Machine with 1gb ram and a 256MB Nvida card.

Thanks so much
Technobia!

When the 2.2 series came out there were features in it pople really wanted - but issues too so dev's have gone back to moving 2.0.13 up to stable and in 2.0.14 icorporate some of the features of the 2.2 series. As they work on the next release they will add more features from the 2.2 series. You could say that there has been good learning from 2.2. 2.2.4 is the one most people still suing 2.2 seem to be happy with, while the rest of us are staying in the 2.0 series and moving into 2.0.14 which is the latest release.

Quote:
It is spotlighted on the news in the front page of xoops.org with a link to the instructions which must be followed exactly. Click the 'read more' on XOOPS 2.0.14 released news item and you will find it.

The general comments also suggests that this will fix your problem number 2 - XOOPS 2.0.14 makes XOOPS go faster.

For more info on the 2.2 series use the search function. HTH

PS: I found xoops.org was incredibly slow on IE but on firefox it was much faster - so you can try a comparison of the two browsers too...

Excelent! Thank you! That was very helpful. I will do the 2.0.14 update and get back if I should have any issues.

One quick confirmation please. I assume from the release notes section heading:

"Upgrading from any XOOPS version between 2.1.10 and 2.0.13.2"

That I DO NOT need to first upgrade from 2.0.13.1 to 2.0.13.2 before applying the 2.0.14 upgarde?

Thanks!

I'm using 2.2.4 on 6 sites, and 2.0.13 on 1, I (personally) love the 2.2.4 admin system, and I havn't had any issues relating to that version.

Speed = XOOPS (and php&sql CMSs in general) are a different world from hosting html sites. You can (and should try searching this site for speed and things like that), but here's some tips:

(assuming you run apache) mod_gzip (http://sourceforge.net/projects/mod-gzip/) this will make a huge difference. it isn't necessary for plain html pages - but is for Xoops. It compresses the files sent to the browser. It will save you 75% - 85% in bandwidth, and your pages will load a TON faster.

eaccelerator - (http://eaccelerator.net/)- everytime a php script is called on a webserver, the script has to be compiled - eaccelerator caches them in a compiled state which cuts down on over head (in my experience it works especially well with Xoops, because XOOPS loads several scripts when loading - this takes out the compile time.

mysql caching - (http://www.databasejournal.com/features/mysql/article.php/3110171)caches common queries to cut down on the number of queries the database has to serve up. not a huge deal - but every little bit helps.

optimizing graphics - (http://www.netmechanic.com/GIFBot/optimize-graphic.htm) - trade off some of the quality of the graphics for speed - this can help a LOT. (check it out, don't just optimize the pictures, do all of the graphics, even forum buttons and stuff.

Some of it can be difficult to setup but just keep tinkering, it is really worth it.

Thanks will check those links out. I am using IIS not Apache

Hi technobia,

Have a look at the Performance Tuning XOOPS on IIS article I wrote a while back. If you have installed on IIS using the standard PHP installer, then it will not be tuned for performance. Using my guide you should be able to reach performance increases of nearly 1000% for PHP execution times.

WOW! Brash,

That is some of the best documentation I have seen, especially for open source! You are a gem!!!!

I have a few questions:

1. Since I enabled HTTP Compression in IIS the sites work fantastic however I have seeing pretty regular spikes in CPU utilization. Is this because perhaps all the sites are not yet compressed? I have 30+ include the XOOPS site which does not seem to be compressed.

2. In installed Zen Optimizer but do not see much of a difference with that. Do I need to do anything else with it?

3. I did not install accelerator as there were no real instructions for Windows 2003 / IIS server. Perhaps you can assist with this and/or location the proper documentation.

I love your website too!!!
Thanks so much Technobia

P.S What is your latest version of AMS (2.4?) I would like to try it? Is it compatable with XOOPS 2.0.14 /PHP4.3.11/ MySQL 4.1?

Quote:

Correct! - I see you have also had some input from some other very savvy xoopsers too...you are on the right track

Quote:

- The XOOPS site is compressed and the rest are not? Or are the rest of them compressed and the XOOPS is not? Either way - compression has to be enabled for each type of site, php for the xoops, and html for the rest. Try this tool to check it: http://www.websiteoptimization.com/services/analyze/