jReviews Support Forum

In jReviews 1.2RC3 the addition of indexes to the jReviews tables and improvements in queries have greatly contributed to better performance, reflected in faster loading pages. Not only that, but also many of the javascript libraries that were unnecessarily being loaded in all jReviews pages, now load only on the ones where they are needed. Another improvement was in the module thumbnails which are not correctly resized to the specified module size setting.

There's always room for improvement and in future version we will do our best to find more ways to decrease the number of queries.

Having said that, one aspect of jReviews which significantly increases the number of queries is the entry count in the directory, entry lists and the modules. By turning this setting off, the number of queries will be reduced significantly and that is the recommended setting: show entry count = NO in the component and modules.

Turning on the built-in Joomla cache will also have a significant improvement in page loads after they have been visited at least once after the cache expiration period.

Also read the performance recommendations at Joomla.org (http://forum.joomla.org/index.php/topic,54175.0.html) and the index queries to boost Joomla performance (http://forum.joomla.org/index.php/topic,159684.msg815459.html)

Thanks for the information.  I was waiting to see if there were any other posts to this topic, but I guess that I am the only one that doesn't quite get it. ???  Where exactly do we "show entry count = NO"?  Do you mean not showing the total listings and reviews in the jrdashboard and sectionnav? 

No, I mean the count that appears in parenthesis next to the category name in the sectionnav module, the dashboard module (not the total listings and reviews mode), the jReviews directory and the jReviews category box. You can see the impact in queries if you enable the debug mode in your Joomla configuration settings.

just in case you have any info abou it.. ;)

does activating the joomla cache affect logged in users as well as guests?

how does the built in joomla cache fare in comparison to 3rd party caching applications (e.g. ircmaxell or joomlaatwork)?

thanks
gigi

I have not tried the other caching applications, so I don't know. The Joomla cache does cache content for logged in users as well as guests.

update on that --> it does cache for logged in users, however, there's some odd behaviors exhibited! formattings disappear, drop-boxes keep resetting, and so on. i'll be forced to turn this off. i'm now testing the ircmaxell's pagecache for non-logged-in caching. if it will cache the products' directory that would be an advantage, and probably as far as it can reliably go at least on my site..

Any update on this? I also try to use ircmaxell's querycache component but I'm still making some tests. Does anyone have any experience?

Thanks,
Serkan

i tried ircmaxell, it didn't cause any problems but i didn't notice a real significant increase in performance either. maybe it shows its merits on heavier sites. you can use it, but if your site is not very big, you can do without caching in my experience.

My problem is with the server load. I'm using a shared server and there are load problems in the server. They say that my site is using to much CPU so I'm trying to solve it.

Pagecache supposed to decrease the page load times I guess but the documentation says that querycache from ircmaxwell is for the load and it has no effect on the page loading times. Hopefully it'l solve my load problems...

Thanks for the reply...

unless you use highly inefficient code, what you need to do first and foremost is to switch hosts. i was hosting my site at one company and my site was very slow with the occasional cpu error. i switched to another company for $4 more / month and now it's almost faster than my local installation! and no cpu exceeded errors.

you can literally have your site run 10 times faster if you choose a good host.

I can imagine that. Even small settings can change a lot. But in my case,  I think the extensions and plugins I use are not very efficient. There are a lot of queries for some pages. I saw 900 queries for a profile page cause there were a lot of items in the Articles tab of CB. This is the most extreme case but I had to work on these first.

Also I live in Turkey and need to find a server located in Turkey or Germany. I tried a server in US and the speed was considerably low. I think we have direct connection with Germany so it works as fast as hosted in Turkey...

900 queries.. something's really wrong there. i have about 100 queries per page and that's considered a lot too.

you would be best asking about this in ircmaxell's forum:

http://www.joomlaperformance.com

or in joomla.org performance forum:

http://forum.joomla.org/index.php/board,268.0.html

gigi

I think it's because of the article tab which has no pagination:) If a user has 300 items, then you have a problem. I also found one with pagination and will try that.

I already wrote in joomlaperformanca and joomla.org forums. But when I see this topic I just wanted to see how it worked for you.

Thanks for sharing your experiences...

You can retrieve 300 rows with a single query, or 1 million for that matter. The problem in this case would be if for every row another query is run. In your case, as an example, for every row, 3 additional queries would result in 900 queries.

So not having pagination doesn't necessarily impact the number of queries, unless you have the situation above, but it does impact memory usage because retrieving 300+ rows is not the same as retrieving 10-50 rows.

I see your point but I compared different profiles and saw that the ones without any items have around 100 queries and number of queries increases with the number of items in that tab.  looks like 2 queries are run for each content item.

I think these queries are run by the function $mainframe->getItemid which is VERY inefficient. It gets the correct menu id (Itemid in the url) for each content, but instead of receiving an array with all the content ids, it is run for each one.

Hi, I just wanted to add that I was experiencing the same problems with joomla cache as gigi.

When I turn it on, some review pages are formatted incorrectly (they are all black and white, as if no css styling was used) and ajax is not working so it's impossible to write a review.

I even saved the same page with cache off (looking ok) and cache on (the aforementioned problems present) and it turned out that the html file size difference is ca. 10 kilobytes i.e. when the cache is on the page size is 10 kb smaller. It looks like  there is a lot missing in the output.

I turned off the cache and never bothered but it would be a nice addition to an overall great package if I could use the cache.

Take care!

Hi,

Has anyone had a chance to go through the code thoroughly and analyzed which application functions slow down performance the most?For example, does adding additional custom fields create additional table joins which in turn degrade performance?

Also,  has anyone analyzed the SQL Explains in order to ensure that indexes are always being used and are being used correctly? In other words, has an SQL expert examined all the queries for logical database and physical database optimization? Has different versions of the MySQL optimizer affected the performance of the system? Thanks for any info.

Rich