Performance & Caching (1.5 -> 3.1)

Mini-calendar - if you have events every day then set it to not check each day for matching events. Its a LOT faster but won't highlight the days with/without events.

It sounds as though you may be using Joomla page caching - is that correct?

There is a club member article about performance and caching - see http://www.jevents.net/docs/jevents/ite ... vents-site . A typical problem for many sites is bots and spiders crawling hundreds of JEvents pages in an uncontrolled way - the article describes remedies for this.

Finally we are working on a major upgrade to the filtering code which will allow it to work with correctly with all forms of Joomla caching whilst preserving the correct session based filtering memory. In the meantime there are config options in JEvents filter module to allow you to actively manage when the filters are reset

Thank you for your quick response !!

No, we dont have Page Caching activated !!! (Built-in Plugin (Extensions -> Plugin Manager -> System - Cache))

But we use view-caching (Global Config->Cache) !!

JEvents 3.1 is quite clever already with respect to session filtering if you don't use page caching. It should work ok with the core Joomla caching enabled (but not the system plugin page cache) so I would recommend you migrate your site (maybe on a test subdomain first) and test it out.

THANK YOU VERY MUCH, i was planning to do this, we already have Joomla/jEvents Site, i will insert the data from 1.5 and test its performance !!

i have see the free documentation for migrating 1.5 -> 3.1, how long will it take to to the data migration?


THANKS !!!! best regards

Depends on your number of events usually less than 1 minute once you have the migration script configured

Please forgive me for butting in, but with regard to caching, I've just spent about a month wrestling this issue to the ground... and I've learned more than I wanted to know about joomla caching etc.

First, and I'm sure that MANY people will tell you this, download and install Jotcache. this will solve about 50% of your issues out of the box that the built in cache does not solve.

This is not and ad for Jotcache... its free. and I have no vested interest other than to say, that after diving deep into the subject, This is THE caching solution for joomla. Don't let it scare you, its pretty complex, but works out of the box. just install it, turn off the system cache (and page cache if you're using it), and you'll notice an amazing improvement over the built in cache. As you get more familiar with it, you will discover the item specific caching features that can really help you tune Jevents performance.

I'd also recommend turning on gzip compression unless you have a reason not to. between this and Jotcache most of your issues will be solved.

Next, if you're using shared hosting, this is also probably effecting you. The situation you describe could cause literally hundreds of calls to the database for each load. Most shared hosting plans will see this, and throttle you... sad but true.

I have Jevents installed for one of my clients with 850+ employees, and they have regular online meetings that involve hundreds of people. (which is the reason I needed to become joomla cache educated). On a VPS server with 4 CPU cores allocated, and nothing else special, my page loads for Jevents pages even with events that involve hundreds of people are under 2 seconds.

Hope this is of some help to you, I know how frustrating these issues can be.

Warm Regards,
Trauncher.