Evergreen DokuWiki

Use the space below to identify areas in Evergreen that would benefit from a performance analysis along with any questions that you would like a performance analysis to answer.

• Cataloging - Clicking Add Volumes or Edit Items/Volume per Bib screen is slow loading (approximate 16 seconds on our production system at C/W MARS)
• Memory leaks - is there an inherent problem with the technology used in the staff client (xulrunner, Dojo) that is the source of the memory leak problem and other performance problems?
  • Testing and development shows that Dojo is not the source of memory leaks. The cause of many seems to be event handlers pinning memory at page unload time, not allowing the GC to free all memory for many interfaces. See: https://bugs.launchpad.net/evergreen/+bug/1086458 for some initial work, and there is more coming.
• Slow retrieval of patron records
  • This looks to be caused by a combination of redundant XHR requests and the use of many XHR requests in general. This theory is corroborated by the speed improvement displayed by an experimental server-side (html) version of the patron sidebar. Details to follow.
• Editing and saving patron records is slow.
• Staff client batch operations (e.g. updates/deletes from copy buckets)
  • Can we get more specifics on this?
    • Sure, here's one example: https://bugs.launchpad.net/evergreen/+bug/921812
    • Hmm, I don't see this ^- as a general problem with Messaging. This is a specific problem with an API call and/or how the client is using it.
    • We get so many "Network Failures" with real world data that I think we have many more of these "specific problems" with how the client handles many such API calls. Deleting from buckets is just one example.

• Displaying records with many items and paging through the items.
  • Do parts exacerbate this problem?
  • Sample record - http://evergreen.noblenet.org/eg/opac/record/2407864

• Catalog search - is there a way to optimize searching in the catalog so that users get faster results and are able to start re-implementing things like search.relevance_adjustment to provide boosts to relevance ranking?
• Optimizing some queries to improve performance - do we have examples of specific queries that can be optimized?