Changes between Version 24 and Version 25 of Ticket #590
- Timestamp:
- 09/07/13 19:20:58 (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #590
- Property Estimated Number of Hours changed from 0.0 to 0.05
-
Ticket #590 – Description
v24 v25 12 12 '''G) Enable ESI (Edge Side Includes) integration module, ensure Drupal renders only what it needs to ''' 3-8 hours, high reward, medium risk -- BOA packages the [https://drupal.org/project/esi ESI (Edge Side Includes integration) module], which makes NginX cache the whole page (as it does now), but also for user-logged in pages (which it does for 5 seconds since the page data changes). This means Drupal renders the ESI component (blocks, panels panes) that are have user-specific data in. Potential boost quickly, but will need time to tweak settings to get best from this across whole site. See [https://tech.transitionnetwork.org/trac/ticket/590#comment:4 comments in 4 & 5 below for discussion], should be done after proposal F, above. 13 13 14 14 15 === New, to run past Ed === 15 16 '''I) Re-enable block caching.''' -- 2-6 hours, high risk, high reward -- Per comment 24, a module (probably Content Access) is stopping Drupal caching blocks, which for some of them means a fair amount of pointless overhead. We need to somehow get around this and get blocks cached if possible. R&D mainly, perhaps with some hacking/patching - but I'd stop short of doing this if so. … … 19 20 20 21 === Done already === 21 '''A) Remove spam taxonomy entries''' 1/2 hour, Low risk, low reward -- See item 8 below. A simple delete from taxo term table where length > 50 is worth doing IMHO, and nothing I saw that would be clobbered is not spam.22 '''A) Remove spam taxonomy entries''' ~~1/2 hour, Low risk, low reward -- See item 8 below. A simple delete from taxo term table where length > 50 is worth doing IMHO, and nothing I saw that would be clobbered is not spam.~~ 22 23 23 '''B) Try a Taxonomy Cleanup''': 3 hours, Medium risk, medium reward -- style module to try to merge terms with the same names and clean up the link tables back to nodes. Further, we can remove any taxonomies or relations to certain CTs that don't really add value.24 '''B) Try a Taxonomy Cleanup''': ~~3 hours, Medium risk, medium reward -- style module to try to merge terms with the same names and clean up the link tables back to nodes. Further, we can remove any taxonomies or relations to certain CTs that don't really add value.~~ 24 25 25 '''D) Review Views caching''' 1-2 hours, low risk, high reward -- this was done a while back but I think -- done (task 12) in comment 21. 26 '''D) Review Views caching''' ~~1-2 hours, low risk, high reward -- this was done a while back but I think -- done (task 12) in comment 21.~~ 27 28 '''F) Force blocks caches to cached appropriately (and be rendered/included only as needed) -- NEEDS I) to complete!'' ''' ~~-- 1-2 hours, medium reward, low risk -- BOA packages the [https://drupal.org/project/blockcache_alter Block Cache Alter], which makes sure Drupal only renders blocks when needed. Potential small but nice boost quickly in whole site. -- per comment 22, block caching is disabled by other modules so this will have to go on hold for now.~~ 26 29 27 30 '''H) Remove CustomError module all together''' ~~1/2 hour, low risk, low reward -- We should take out the PHP code from the 403 section of CustomError and put it into a simple page entry. See comment 6 below as this has happened for 404s (which need no PHP). We can then remove the CustomError module all together, saving lots of sessions. I would go ahead and do this but since the 403 page has various displays depending on user type, I wanted to raise it here as it *may* have side effects. Or not...~~ … … 34 37 * '''E.1) Remove 'Geographic region' and related taxonomy and Hierarchical Select modules''' 1 hour, low reward, low risk -- never really been used and is effectively a duplicate of the location field. let's kill it! 35 38 * '''E.2) Kill Microsites and the Forums''' -- 3 hours, low risk, '''game changer/needs confirmation''', high reward: -- then remove OG and Forum modules. In D6 these are known to be performance killers. We could alternatively migrate the forum to a simpler setup (not using forum module) that leverages Disqus or other services to offload comments and moderation. Either way, the handful of people using the CMS feature should be migrated to Open Atrium if they need such features. 36 37 38 '''F) Force blocks caches to cached appropriately (and be rendered/included only as needed)''' 1-2 hours, medium reward, low risk -- BOA packages the [https://drupal.org/project/blockcache_alter Block Cache Alter], which makes sure Drupal only renders blocks when needed. Potential small but nice boost quickly in whole site. -- per comment 22, block caching is disabled by other modules so this will have to go on hold for now.
