Difference between revisions of "Optimizing the performance of your JReviews site"

From JReviews Documentation
Jump to: navigation, search
(Created page with "The performance of a site depends on many factors that range from hardware to the scripts running on the site. '''If you have a large database and growing traffic consider movi...")
 
 
(3 intermediate revisions by 2 users not shown)
Line 11: Line 11:
  
  
−
'''Sites with large data sets must avoid using any modules or pages that display random results'''
 
  
−
This includes the random modes for JReviews modules as well. In the worst case scenario for RAND() ordering MySQL requires a full table scan which can be very slow with a large number of records.
+
'''When using the GeoMaps module, avoid having thousands of markers displaying at once'''
  
 +
Rendering each marker takes time and affects load time. The add-on will eventually be re-written to load the map via ajax after the page finishes loading, but until that time you should know that the more markers displayed on the map, the slower the page.
  
−
'''Create additional indexes in Joomla tables'''
+
'''Sites with large data sets must avoid using any modules or pages that display random results'''
−
 
+
−
For JReviews in particular the following indexes will help speed up performance for some of the database queries.
+
−
 
+
−
 
+
−
<source lang="sql">
+
−
ALTER TABLE `jos_content` ADD INDEX `listing_count` ( `sectionid` , `catid` , `state` , `access` , `publish_up` , `publish_down` );
+
−
 
+
−
ALTER TABLE `jos_content` ADD INDEX `published` ( `state` , `catid` );
+
−
 
+
−
ALTER TABLE `jos_categories` ADD INDEX ( `title` ( 35 ) );
+
−
 
+
−
ALTER TABLE `jos_sections` ADD INDEX ( `title` ( 35 ) );
+
  
−
ALTER TABLE `jos_content` ADD INDEX `created` ( `created` );
+
This includes the random modes for JReviews modules as well. The worst case scenario for random ordering in MySQL requires a full table scan which can be extremely slow with a large number of records.
  
−
</source>
+
[[Category:JReviews]]
 +
[[Category:Joomla]]
 +
[[Category:Performance]]

Latest revision as of 23:13, 3 November 2011

The performance of a site depends on many factors that range from hardware to the scripts running on the site.

If you have a large database and growing traffic consider moving to a VPS or dedicated server

Shared environments limit the resources allocated to your site and sometimes host hundreds of other sites on the same server.


Avoid installing dozens of modules and plugins on the site. Keep only those that are indispensable

Everything you install on your Joomla site consumes resources and degrades performance. That includes components, modules and plugins. The more scripts you have running on the page, the more resources that page will use.


When using the GeoMaps module, avoid having thousands of markers displaying at once

Rendering each marker takes time and affects load time. The add-on will eventually be re-written to load the map via ajax after the page finishes loading, but until that time you should know that the more markers displayed on the map, the slower the page.

Sites with large data sets must avoid using any modules or pages that display random results

This includes the random modes for JReviews modules as well. The worst case scenario for random ordering in MySQL requires a full table scan which can be extremely slow with a large number of records.

Retrieved from "https://docs.jreviews.com/index.php?title=Optimizing_the_performance_of_your_JReviews_site&oldid=2256"