Changes between Version 5 and Version 6 of Ticket #590


Ignore:
Timestamp:
09/06/13 15:03:29 (3 years ago)
Author:
jim
Comment:

I just realised that 404 pages START A FREAKING SESSION!

E.g. go to any page in the site, no session cookie... Go to a 404 like ​http://www.transitionnetwork.org/asses-of-doom and there's a session cookie.

THIS IS BAD! So new action:

10.. After checking the CustomError? module is starting a session on 404 pages, causing general slowness. So I've:

According to running SELECT COUNT(*) FROM sessions WHERE uid = 0; against the database, there are currently 2489 anonyomous sessions active over the last 2 days. This fix should have the effect of stopping 404s generating new ones for anonymous users, which I reckon is many of them.

This brings me to proposal H above, regarding doing this for 403s and removing CustomError? all together.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #590

    • Property Add Hours to Ticket changed from 0.35 to 1.0
    • Property Total Hours changed from 2.95 to 3.95

  • Ticket #590 – Description

    v5 v6  
    2323 
    2424'''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. 
     25 
     26'''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...