Note: You are currently viewing documentation for Moodle 2.1. Up-to-date documentation for the latest stable version is available here: Performance settings.

Performance settings: Difference between revisions

From MoodleDocs
Main page ► Managing a Moodle site ► Performance ► Performance settings
Performance
Newer edit →
VisualWikitext
performance template, performance settings, Other site administration settings which may affect performance moved from Performance recommendations
 
Line 6: Line 6:
==Other site administration settings which may affect performance==
==Other site administration settings which may affect performance==


* Enable the '''language cache'''.
* Make sure caches are used (most are default)
** ''Cache language menu'' and ''Cache all language strings'' in Settings > Site administration > Language > Language settings.
** ''Cache javascript'' in Settings > Site administration > Appearance > AJAX and javascript
* Make sure ''Theme designer mode'' is '''Off''' in Settings > Site administration > Appearance > Themes > Theme settings (unless you are editing a theme of course!)
* Large log files can cause overall performance to degrade over time. If you observe that the site has gradually got slower loading pages in the browser, '''reduce your Log life time''' setting in ''Settings > Site administration > Server > Cleanup''
* Large log files can cause overall performance to degrade over time. If you observe that the site has gradually got slower loading pages in the browser, '''reduce your Log life time''' setting in ''Settings > Site administration > Server > Cleanup''
* Performance can be greatly improved by allowing Moodle to use the system '''zip/unzip''' commands (rather than PHP-based zip libraries) - visit Admin/Server/System Paths and enter the path to the relevant executables. (Similarly, filling in the path to '''du''' will improve Moodle's speed at listing directory contents.)
* Using '''secure web connections''' ('''https''' rather than '''http''') carries a higher processing burden, both for the webserver and the client - particularly because cacheing cannot be used as effectively, so the number of file requests is likely to increase dramatically. For this reason using https for all Moodle pages is not recommended. You can enable https just for the login screen, simply from Moodle's config page.
* Note that using '''secure web connections''' ('''https''' rather than '''http''') carries a higher processing burden, both for the webserver and the client - particularly because cacheing cannot be used as effectively, so the number of file requests is likely to increase dramatically. For this reason using https for all Moodle pages is not recommended. You can enable https just for the login screen, simply from Moodle's config page.
* Check your '''filters'''. Having too many filters active can have serious effects on server load, especially on lower-end systems. The number of active filters has a direct effect on the perceived latency of your site; that is the time taken for each page impression.  
* Check your '''filters'''. Having too many filters active can have serious effects on server load, especially on lower-end systems. The number of active filters has a direct effect on the perceived latency of your site; that is the time taken for each page impression.  
* Enable the '''text cache''' but do not "Filter all strings" unless you have a specific need. If in doubt profile the performance, and see how your changes affect the processing time.
* Check your '''anti-virus''' measures on the server.  Although they are useful for preventing security holes being exploited, some "On-Demand" scanners can affect performance by scanning page content (word, ppt files etc).
* Check your '''anti-virus''' measures on the server.  Although they are useful for preventing security holes being exploited, some "On-Demand" scanners can affect performance by scanning page content (word, ppt files etc).
* If there are performance problems loading course pages, check the '''Resource module settings'''. The setting resource_filterexternalpages is known to slow-down course pages and should be set to 'No' for better performance.
* Check your '''forum settings''' in Settings > Site administration > Plugins > Activities > Forum. To improve performance set ''Track unread posts'' to  '''No'' (although the user's will loose the ability to track unread posts).
* Check your '''forum settings'''. To improve performance set forum_trackreadposts = No and forum_usermarksread = Yes (this will impact on the convenience of your users' forum experience). Also consider setting the time of the day when old posts are cleared from the read table (forum_cleanreadtime) to when your site is less busy.
* Don't use database sessions unless you really need them. On-disc sessions tend to be much faster.
* Don't use database sessions unless you really need them. On-disc sessions tend to be much faster.

Revision as of 17:15, 4 December 2011

Performance settings

Various performance settings can be changed by an administrator in Settings > Site administration > Server > Performance.

Other site administration settings which may affect performance

  • Make sure caches are used (most are default)
    • Cache language menu and Cache all language strings in Settings > Site administration > Language > Language settings.
    • Cache javascript in Settings > Site administration > Appearance > AJAX and javascript
  • Make sure Theme designer mode is Off in Settings > Site administration > Appearance > Themes > Theme settings (unless you are editing a theme of course!)
  • Large log files can cause overall performance to degrade over time. If you observe that the site has gradually got slower loading pages in the browser, reduce your Log life time setting in Settings > Site administration > Server > Cleanup
  • Using secure web connections (https rather than http) carries a higher processing burden, both for the webserver and the client - particularly because cacheing cannot be used as effectively, so the number of file requests is likely to increase dramatically. For this reason using https for all Moodle pages is not recommended. You can enable https just for the login screen, simply from Moodle's config page.
  • Check your filters. Having too many filters active can have serious effects on server load, especially on lower-end systems. The number of active filters has a direct effect on the perceived latency of your site; that is the time taken for each page impression.
  • Check your anti-virus measures on the server. Although they are useful for preventing security holes being exploited, some "On-Demand" scanners can affect performance by scanning page content (word, ppt files etc).
  • Check your forum settings' in Settings > Site administration > Plugins > Activities > Forum. To improve performance set Track unread posts to No (although the user's will loose the ability to track unread posts).
  • Don't use database sessions unless you really need them. On-disc sessions tend to be much faster.
Retrieved from "https://docs.moodle.org/21/en/index.php?title=Performance_settings&oldid=94477"
Powered by MediaWiki