If you're experiencing slow page loads, there are several layers you need to look at to identify the cause. Take a look at performance troubleshooting guide to go through each of the layers and identify your culprits.
Using caching to improve API performance
Deki Wiki has several built in caching mechanisms you can take advantage of to speed up page loads if you notice that the Deki's page execution speed is your problem. Enable profiling (described in the troubleshooting guide) and take a look at the overall and API time. Note that overall execution time = API time + PHP time. If your API time is over .1 seconds or so, you may want to consider enabling some of these cache settings.
To enable these, login to the wiki as an administrator. Go to control panel -> configuration. Add the follow key/value pairs:
- cache/roles bool
- Enable caching of permission roles to reduce database calls. (default: false)
- cache/services bool
- Enable caching of authentication providers and extensions to reduce database calls. (default: false)
- cache/users bool
- Enable caching of user data to reduce database calls. (default: false) cache/bans bool
- Enable caching of bans to reduce database calls. (default: false) cache/anonymous-output bool
- Enable caching of generated output for the anonymous user for several API calls. This will greatly improve performance for anonymous users at the cost of their data being slightly out of date. This is very useful for internet sites experiencing a burst of anonymous users. (default: false) cache/anonymous-output-short integer
- If cache/anonymous-output is enabled, this is the time in seconds to cache the shorter ttl calls described below(default: 300) cache/anonymous-output-long integer
- If cache/anonymous-output is enabled, this is the time in seconds to cache the longer ttl calls described below(default: 3600)
Misc settings to improve API performance
- stats/page-hit-counter bool
- Controls updates to each page's hit counter. Setting to false will reduce load on the DB by being able to more effectively use the query cache at the cost of the popular pages feature. (default: true)
Improve UI performance by installing a PHP accelerator
We've had good results with eAccelerator but any of them should work.
Improve overall performance with a caching reverse proxy
Setting up Varnish or Squid will allow you to serve a huge amount of anonymous traffic very quickly.
Performance related bugs
Deki API
| Bug# | Summary | Status | Opened By | Assigned To | Severity |
|---|---|---|---|---|---|
| Replace stored procedures with inline SQL queries | closed | RoyK | MaxM | minor | |
| DB Query and entity population | closed | MaxM | MaxM | major | |
| Deki XML Parser optimizations | closed | MaxM | MaxM | minor | |
| Misc optimizations to 8.05.1 | closed | MaxM | MaxM | minor | |
| New cache and optimization settings introduced in 8.05.1 | closed | MaxM | MaxM | minor |
Deki UI
| Bug# | Summary | Status | Opened By | Assigned To | Severity |
|---|---|---|---|---|---|
| Remove time offsets from UI | closed | RoyK | RoyK | minor | |
| Consolidate JS methods to use jQuery | closed | RoyK | RoyK | minor | |
| Move assumed styles out of general.css | closed | RoyK | RoyK | minor | |
| Consolidate onbody load methods | closed | RoyK | RoyK | minor | |
| UI caching does not expire on release updates | closed | Guerric | Guerric | minor | |
| Audit Javascript includes | closed | RoyK | RoyK | major | |
| Cache the language loading in PHP | closed | RoyK | mozhechkov | minor |
- Tag page
- What links here
You can check your MySQL cache settings with the following command while in MySQL command mode:
mysql> show variables like 'query%';
edited 00:58, 12 Jun 2008