Hi all,

I'm still rather new to XOOPS and need some advice, please.

I'm getting complaints from some of site my users that my site takes ages to load and sometimes times-out. I'm reasonably certain that this is a server issue, but would like to do all I can to speed things up before I "have a go" at the hosting company.

I've run debug and the following might be of interest:

In amongst 9 other "Notice" type errors were these three:

Warning: Missing argument 2 for auto_summary() in file /modules/news/class/class.newsstory.php line 1121
Warning: Missing argument 2 for auto_summary() in file /modules/news/class/class.newsstory.php line 1121
Warning: Missing argument 2 for auto_summary() in file /modules/news/class/class.newsstory.php line 1121

I'm running News 1.50. Are these errors important and would they slow down page load? Should I report this to the module's dev team? Anyone fixed this?

Is 57 queries on the homepage excessive?

I have 17 blocks on the homepage - too many?

The timers say:

XOOPS took 4.196 seconds to load.
XOOPS Boot took 0.687 seconds to load.
Module init took 0.008 seconds to load.
XOOPS output init took 3.465 seconds to load.
Module display took 0.011 seconds to load.
Page rendering took 0.022 seconds to load.

All advice and help much appreciated, and thanks in advance

Make use of gzip-compression and/or use caching for blocks and modules where it is appropriate, e.g. seldom refreshed blocks/content.

Quote:
The first is the module's actual loading time
The second "XOOPS output" is initiating the output layer (Smarty) AND the blocks.

It seems you have a great amount of blocks that take quite some time to load. Find out which and see if you can cache them.

This is a good question. I have read a fair bit of generic advice to cache blocks and modules, but it would be great to hear of some recommended settings.

For example, if a block is only going to change once a year (e.g. a custom welcome block) I assume you could safely set the cache to '1 month' without spoiling a user's experience of visiting the site. But what about blocks that display 'recent items'? If you add a new item once a day, do you cache the module AND the block to '1 day', or is that too much?

I ran debug on a XOOPS 2.0.13.2 localhost site I'm building which has 10 blocks on the homepage, inc recent news and recent articles. I get 32 queries and XOOPS load tme of 0.435 seconds. I don't see the advanced report (module init etc).

Thanks FrankBlack - I've turned on GZip compression and will see if that helps.

Quote:

The blocks that are loading are mainly "system" blocks. Full list below, with module in ( ):

1. Search: No Cache (system)
2. Main Menu: No Cache (system)
3. Custom Block (Auto Format + smilies): No Cache
4. User Menu: No Cache (system)
5. Login: No Cache (system)
6. Site Info: No Cache (system)
7. Recent Topics: No Cache (CBB 3.07)
8. In the Spotlight !: No Cache (SmartSection 2.12 RC1)
9. Recent News: No Cache (News 1.50)
10. New Members: No Cache (system)
11. Recent Comments: No Cache (system)
12. Minical: No Cache (ExtCal 1.58)
13. Recent items List: No Cache (SmartSection 2.12 RC1)
14. Top Posters: No Cache (system)
15. Upcoming event: No Cache (ExtCal 1.58)
16. Who's Online: No Cache (system)
17. Stats Counter: No Cache (iStats 2.2)

Hmmmm.....this is surprising - News 1.50 and SmartSection 2.12 RC1 are set to 30min cache in admin>preferences. do I need to cache individual blocks as well?

Very grateful for the advice guys. Keep 'em coming, though

I think that much of my problem is server-related because at times the site really flies along and other times its like a slug on beta-blockers

block caches need set separately from module caches
Also, make sure you have MySQL cache enabled.

Keep in mind, if you run a high volume traffic site, do not use the original newbb blocks on homepage.
The newbb query is to be improved in CBB 4.0 for large scale sites.

And, the "mainmenu" block is not recommended. Make your own menu block with mutlimenu or custom block.

Yeah, block cache is set individually on each block.

The following blocks seem like ripe candidates for a 30 minute/maybe longer caching:



Depending on the speed of replies in the topics, the "Recent Topics" and "Recent Comments" may only be useful with 1 or 5 minute caching.

Thanks guys, I'll take a longer look at it this evening/weekend, but if you guys could spare a moment to answer the stuff below I'd be grateful

Quote:

How/where do I do this? Don't recall seeing this as a setting in xoops.

Quote:

Does CBB 3.07 run the "original newbb blocks"? I have a low volume site at the moment.......

Quote:

That's quite a grenade to lob at us humble XOOPS users, mate

Also have a read on some of my latest XOOPS Dev, I have doubled or tripled XOOPS speed...

You can use .js Files for html and it loads as pre-cache then in your theme....especially if you include the foreach of any blocks....inside a .js....

You can also add extra indexing to MySql, where most calls will be needed; so all needed information is in MySql Pre-indexed instead of it searching the data each time for it....it all can be stored by adding an index to a table such as titles ect

May sound complicated, yet most isn't really as I did it and I am not the brightest Xooper

Eek

Quote:

Go on fella, give us a link

Sounds complicated to me, though