EposPerformance
Revision as of 16:02, 14 October 2006 by 195.137.17.58 (talk)
Contents
EPOS system Performance
Main page
- Uses 6 Queries
- Relativly slow queries
- Speed not so much of an issue
Blank Sell tickets page
- Uses 7 Queries
- Makes good use of query cache
- Checkes both DM rotas AND steward rotas **FIXME**
- Do we really need to check everything if we have a valid till session
Crew Sell tickets page
- Uses 23 Queries
- Slowest is member search
- Duplicates multifilm parent id query **FIXME**
- Checks availablity of tickets twice. Once for preselection, once for display **FIXME**
Socs fed non-member sell tickets page
- Uses 25 Queries
- No time info on union db check
- presumably also an ldap check
- Same duplication as crew tickets
Member sell tickets page
- Uses more than 30 Queries
- 3 queries per ticket type and more for passes