Differences

This shows you the differences between two versions of the page.

--- tutorials:speeding_up_pages:start [2010/05/17 14:42]
james
+++ tutorials:speeding_up_pages:start [2014/10/29 23:31] (current)
geojames
@@ Line 2: / Line 2: @@
 There are a few things you can do to help speed up your site, that are highly recommended on high traffic sites.
+**Quick Checklist:**  Click on each item for section giving full details.
+  * [[#turn_off_new_icon_feature|Turn off new icon]]
+  * [[#category_levels_displayed_in_category_dropdowns|Lower # of category levels displayed]]
+  * [[#caching_system|Turn Cache ON]]
+  * Turn SEO setting "Convert Accents" OFF((In **Addons > SEO > General Settings**, un-check box for **Convert Accents**.  Due to the advanced string manipulation required, this feature greatly increases the amount of time it takes to re-write all the URLs on the page to be search engine friendly.))
+  * [[#set_up_cron_heartbeat|Configure Cron Heartbeat]]
 ===== Turn off "New Icon" Feature =====
@@ Line 9: / Line 16: @@
 [[admin_menu/site_setup/browsing_settings/start|Site Setup > Browsing Settings]]
-Change the setting **"New Listing" Time Limit:** to the first selection, **no display of new listing icon**.
+Change the setting **"New Listing" Time Limit:** to the first selection, **no display of new listing icon**.  The new icon requires it to "count" the number of listings in each category placed within a certain time period "on the fly", which creates a huge load on the database for high traffic sites.  To a lesser degree **this is true for category counts** as well, since when a site filter is applied, it requires the software to count the number of listings in a category "on the fly".  If your site makes heavy use of filters such as Geographic Navigation, Zip Search, etc. **you may consider turning off category counts** to speed page load times.
-===== Many Modules Attached But Not Found (v4 or earlier only)=====
-One of the main reasons that pages can become slow to load (at least because of admin configurations) are the number of modules built on a specific page.  When a module is attached to a page in the **PAGES MANAGEMENT** admin tool that module is "built" when a client browses that page on the client side.  After building that modules functionality the script then places that output where that modules placement tag is within the design.  Building the modules functionality is not a problem if you actually used that functionality within the design.
-When you visit any of the pages within the **PAGES MANAGEMENT** admin tool you will find all of the modules attached to that page.  As you develop your design in the page template and html modules the system will automatically attach modules it finds in any page template or html module.  The problem is that the system does not automatically remove a module if it has been removed from the page template or html module.  So after several changes and additions to a page template or html module adding and removing modules to get the design you want there may be several modules attached to a specific page but labelled "not found".  It is then necessary to manually remove the "not found" modules so that they do not slow down the script.
-When you save a change to a page template or html module within the admin tool that template or html is scanned for other modules within it.  Once all of the modules are found every page that template or module is attached to is checked to see of the "found" modules are attached to those pages or not.  If they are not already attached they are attached at that time.  So if you use a module within a template or html module you will need to visit every page that template or html module was ever attached to remove that module if you decide later to not use that module in your design.
-The only time a module may be labelled "not found" yet may still be in use on a page is if a module appears in a subcategory page template but not the default site wide template.  You may need to manually attach modules that only appear in subcategory page templates to make sure that content is ready for placement in the design when that specific category page template is used.
 ===== Category Levels Displayed in Category Dropdowns =====
@@ Line 44: / Line 40: @@
 [[http://geodesicsolutions.com/support/wiki/admin_menu/site_setup/cache/start|Cache Explanation]]
-===== Template System Configuration =====
+===== Set up Cron Heartbeat =====
-You can speed up your site and reduce stress on your MySQL server by switching to file-based templates.  There are caveats to using the file-based template system and this page of the wiki should explain how that feature works:
+By default, the software will send a "signal" to run the cron heartbeat((Basically, the **cron heartbeat** is responsible for doing all the normal "bookkeeping" type things, like closing listings, sending out notification e-mails, etc.  Without it, a lot of things would never get done in the software.)) every time someone views a page in the software.  This is done so that the cron heartbeat gets run and works even on servers that do not have ability to use cron tasks.  If you have a high traffic site however, this can really bog down the site as each page load results in 2 loads, one to display the page, and another to run the heartbeat.  You can improve this greatly by setting up a cron job on your server to run the heartbeat once a minute or so.  See the page below for more information on how cron jobs and the cron heartbeat works:
-[[http://geodesicsolutions.com/support/wiki/admin_menu/templates/template_system/start|File-Based Template Use]]
+[[/admin_menu/site_setup/cron_jobs/start|Cron Jobs]]
-===== Set up Cron Heartbeat =====
+===== Reduce Uploaded Image Size =====
-By default, the software will send a "signal" to run the cron heartbeat((Basically, the **cron heartbeat** is responsible for doing all the normal "bookkeeping" type things, like closing listings, sending out notification e-mails, etc.  Without it, a lot of things would never get done in the software.)) every time someone views a page in the software.  This is done so that the cron heartbeat gets run and works even on servers that do not have ability to use cron tasks.  If you have a high traffic site however, this can really bog down the site as each page load results in 2 loads, one to display the page, and another to run the heartbeat.  You can improve this greatly by setting up a cron job on your server to run the heartbeat once a minute or so.  See the page below for more information on how cron jobs and the cron heartbeat works:
+This support wiki page explains [[startup_tutorial_and_checklist:feature_configuration:file_upload:reducing_image_file_size|lowering image quality to reduce image file sizes used by the software]]
-[[/admin_menu/site_setup/cron_jobs/start|Cron Jobs]]
+=====Implement New Features in v7.3 onward=====
+These changes include changes to "minify" all your css and js files into one smaller file.  Then also to force any non essential css/js for opening page load to be moved to the footer of the design so it may be loaded last.  Those features can be found here in the admin tool:
+  DESIGN > SETTINGS > Combine, Minify, and Compress CSS and JS (Recommended for Live Sites)
+  DESIGN > SETTINGS > Use {footer_html} to delay loading of certain javascript

Geodesic Solutions Community Wiki

User Tools

Site Tools

Differences

Page Tools