tag list limited to 80?

[seadhna]

Hi there,
there seems to be a cap for displaying all articles with a particular tag? It seems to max out at 80?

[datahell]

Tags page has no pagination, so it is not wise to display too many articles as the process is CPU consuming.
I believe 80 articles are enough as they are also ordered based on their creation date (newer first). So the users focus on most recent articles.
I don't know how many people will continue reading after the 10th or 20th article. This is why I believe that the hard limit of 80 is 100% fine.
Of course you can change "80" to anything you want in content.model.php file, although I advise you not to do it.

[seadhna]

Ok, thanks! I should probably approach it in a different way - create new categories... - just when you mention CPU consuming - does it slow down the website to have a lot of modules? I am creating quite a lot at present for a website to allow a 'by the same author' module - so I am creating one for each author (about 50 total).

[datahell]

Enable cache on modules that can be cached and set a good cache life time. The best value depends on your site traffic and the frequency the data are updated.

When we use cache and when not.
We cache items that do not change frequently or dynamically and they are complex or execute many database queries. If for example you have a "latest articles" listing module and you add 3-4 new articles per day you can cache this module for 4-6 hours. If you rarely add new article raise cache time up to 24 hours. If you add 1 or more articles per hour set cache to 1 hour or less. Also we enable cache only when we have high traffic and on items that are been displayed frequently (eg. front-page items). For example if a module is in an internal page where only 5-6 people see it per day there is no reason to enable cache for it because the caching process is heavy and instead of speed up your site it will slow down your site.

Elxis on item without cache (normal speed):
Execute php code + execute db queries > generate html code > display html code

Elxis on caching item (slow speed):
Execute php code + execute db queries > generate html code > save generated code into Elxis repository > display html code

Elxis on cached item (high speed):
get cached html code from repository > display html code

[seadhna]

Thanks datahell. Just to check: when I go to parameters for a module, the options for cache are yes/no and duration. An option for duration is 'global settings'. Where is this defined? Is it in the main settings from main menu - cache tab? i.e. that is default to 15 minutes?
Thanks!

[datahell]

Yes, the default cache time is set in Elxis configuration.

Cache should be enabled only on modules that don't need always to be refreshed. For example you should never enable cash on the login or language modules. The cache lifetime is also very important, if you set the lifetime too soon and you dont have high traffic you might end up with a slower site instead of a faster one. How to set the proper cache life time? Depends on the item and the importance of its contents. If for example we have a module displaying content that changes 2-3 times per day a good life time would be 3-4 hours. You can even set 1 day for items that change more rarely. Elxis also provides you the option to enable cache only for site visitors and not for logged in users.