Troubleshootingslowwebaccess

From CoolSolutionsWiki

-my other wikis

Troubleshooting slow webaccess.

  1. Define what the end user considers "slow".
    1. 2-20 seconds
  2. Is it slow for external as well as internal users?
    1. webacc is a bit slower than apache - from webmetrix perspective (po0, changed user, still same result)
  3. Does the slowness affect all users on all Post Offices?
    1. not a particular PO
  4. Is it limited to 1 User, 1 Post Office or 1 Domain.
    1. NA
  5. Which part is slow? auth? browsing webaccess? view/downloading attachments?
    1. NEEDINFO (recently disallowed VIEWER)
  6. X ensure all links are healthy in gw http monitor
  7. X look at PO threads and logs for general GW health
  8. consider dividing agent and application across different servers
    1. agent is on NW, app is on linux
  9. update code
  10. check disk IO
  11. ensure LAN. if 100 ensure forced 100 full duplex. if 1000, ensure switch is HARD SET for 1000 FD
  12. SSL?, LDAP?
  13. What has changed? Did it work in the past?
    1. started noticing after mgr's tool to time logins.
  14. Is the slowdown time sensitive? IE, Always happens @ 6 pm...

need info

  1. get reports, trends on when slow
  2. interview end-user
  3. screen shot of webaccess http monitor stats WHEN it is reported to be slow
  4. NRM reports
  5. load config.nlm /all