Changes between Version 34 and Version 38 of Ticket #590


Ignore:
Timestamp:
09/10/13 12:10:05 (3 years ago)
Author:
jim
Comment:

OK, found this: http://2bits.com/admin-menu/admin-menu-module-popular-yet-occasionally-problematic.html and https://drupal.org/node/1031950

Hence, I'll do this (Proposal N) when #582 happens: Replace Admin Menu 1.x with 3.x -> could be the cause of some load spikes as it occasionally goes made and does 2000-5000 queries! Added to #582

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #590

    • Property Add Hours to Ticket changed from 0.5 to 0.1
    • Property Total Hours changed from 14.2 to 14.65
  • Ticket #590 – Description

    v34 v38  
    99'''L) Review slow query log, explain queries, tweak as necessary/flag poorly behaving modules.''' 2-4 hours, high reward, low risk... Keep looking at the slow query log and adjust Drupal or find patches as necessary. ALSO related [http://2bits.com/articles/reduce-your-servers-resource-usage-moving-mysql-temporary-directory-ram-disk.html Reduce your server's resource usage by moving MySQL temporary directory to tmpfs]... Have opened ticket for this: #591 for Chris. 
    1010 
    11 '''M) Take control of Cron, and maximise time pages are cached for.''' .25h, high reward, low risk -- ~~Cron is wiping the page cache, so we need to install https://drupal.org/project/elysia_cron so we can clear the page less often, and run other things when we want and the site is quieter.~~ Now need per minute resolution set to get the best, see comment 33 and 34 for more... 
    12  
     11'''N) Replace Admin Menu 1.x with 3.x''' 5 mins, high reward, low risk -- done when #582 happens, could be the cause of some load spikes as it occasionally goes made and does 2000-5000 queries! 
    1312 
    1413=== New, and to run past Ed === 
    15  
    1614'''J) Convert inline PHP into module code and features''' -- various parts (1-2 hours for block code; 4-6 hours to make Features be used across site), high reward, low risk -- {{{Eval()}}}uated code is much slower than PHP in files, especially since it can't be accelerated by APC or Zend Opcode cache... We have a few blocks and many views that are loaded from the database and evaluated. Ideally the blocks would be moved to the 'Transition Extras' module, and the views would be pushed into features. This work is good to do for maintainability and D7 upgrades, too. See: http://2bits.com/api/abuse-drupal-best-practices-your-own-peril-poor-performance.html and http://2bits.com/articles/free-your-content-php-moving-php-code-out-blocks-views-and-nodes.html 
    1715 
     
    3836'''K) Add & enable Views Lite Pager on big views.''' ~~1 hour, low risk, low reward -- Using this module stops a heavy count query on views with pagers -- recommended for large sites.~~ 
    3937 
     38'''M) Take control of Cron, and maximise time pages are cached for.''' ~~.25h, high reward, low risk -- Cron is wiping the page cache, so we need to install https://drupal.org/project/elysia_cron so we can clear the page less often, and run other things when we want and the site is quieter. Now need per minute resolution set to get the best, see comment 33 and 34 for more...~~ 
     39 
    4040 
    4141=== On hold for now ===