Changes between Version 1 and Version 4 of Ticket #369


Ignore:
Timestamp:
12/05/11 17:48:27 (5 years ago)
Author:
jim
Comment:
  • I've added (outside Git since it's since been removed) the DB Tuner module.
  • I've told it to add any missing recommended indexes.
  • It's got LOTS of hints for MySQL setup/config here: ​https://www.transitionnetwork.org/admin/settings/dbtuner/mysqltuner -- its output is attached as mysqltuner.log
  • Also did the above on workspaces and sharing engine, removing DB Tuner after I added the indexes.
  • ensured sharing engine and workspaces have same session duration, plus improved caching in SE.

See attached mysqltuner.log for handy mysql config tips!

(also updated ticket details, reordering striking and adding where needed.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #369

    • Property Add Hours to Ticket changed from 0.5 to 0.75
    • Property Total Hours changed from 0.5 to 1.75
    • Property Cc ed added

  • Ticket #369 – Description

    v1 v4  
    11Per TTech discussion, some easy/quick things we can do to improve the site's performance... In rough order of ease technically and politically: 
    22 
    3  1. Disable Drupal DB Logging, switching to SysLog instead. -- Small but consistent boost, especially when under heavy load... We'd need a dev-friendly way of viewing the logs though. Very quick change. 
    4  1. Trawl SQL logs for slow queries, find out what's causing them and eradicate the cause -- tough job but potentially huge returns. 
    5  1. Add flood control/DoS blocking and other temporary blocks at the server level if an IP address or crawler bot is taking the piss. A job for Chris. 
    6  1. Lower session timeout to 1 day from whatever it is now -- PHP settings or settings.php tweak, quick-ish job for me/Chris. 
    7  1. Enable more caching for panels/views -- this job is simple but long-ish... Many are done, some left to do. 
    8  1. Go on a module cull -- This is hard and slow, and will result in a loss of functionality. But some modules could be dropped if there's a will. 
    9  1. Massively shrink site CSS -- Small performance increase for 'normal' users, BIG gains for older computers and mobile devices - As Laura points out, better than lots of images, but it still needs to re-use CSS rules/selectors where possible and throw out legacy code. 
    10  1. Enable Throttle module to auto-disable modules during heavy loads -- Throttle gets a bad press and can cause issues, 
    11  1. Disable Piwik and use Google Analytics instead. Chris is opposed to this but server resources are at a premium unfortunately. 
    12  1. Force HTTP only for non-logged in users (explained above) -- BIG boost, quick settings change, though might need Chris to alter htaccess/varnish setup. 
    13  1. Switch to NGINX -- Chris thinks this is a lot of work, see #357 
     31. ~~Disable Drupal DB Logging, switching to SysLog instead. -- Small but consistent boost, especially when under heavy load... We'd need a dev-friendly way of viewing the logs though. Very quick change.~~ 
     42. Trawl SQL logs for slow queries, find out what's causing them and eradicate the cause -- tough job but potentially huge returns. 
     53. Add flood control/DoS blocking and other temporary blocks at the server level if an IP address or crawler bot is taking the piss. A job for Chris. 
     64. ~~Lower session timeout to 1 day from whatever it is now -- PHP settings or settings.php tweak, quick-ish~~ 
     75. ~~Enable more caching for panels/views -- this job is simple but long-ish... Many are done, some left to do.~~ 
     86. ~~Add indexes to tables where needed.~~~ 
     97. Do config/performance enhancement ideas in {{{mysqltuner.log}}} 
     108. Massively shrink site CSS -- Small performance increase for 'normal' users, BIG gains for older computers and mobile devices - As Laura points out, better than lots of images, but it still needs to re-use CSS rules/selectors where possible and throw out legacy code. 
     119. Disable Piwik and use Google Analytics instead. Chris is opposed to this but server resources are at a premium unfortunately. 
     1210. Force HTTP only for non-logged in users (explained above) -- BIG boost, quick settings change, though might need Chris to alter htaccess/varnish setup. 
     1311. Enable Throttle module to auto-disable modules during heavy loads -- Throttle gets a bad press and can cause issues, 
     1412. Go on a module cull -- This is hard and slow, and will result in a loss of functionality. But some modules could be dropped if there's a will. 
     1513. Switch to NGINX -- Chris thinks this is a lot of work, see #357