Page History

...

• Chris walked us through early performance testing results at https://cwilper.github.io/dspace-perftest/
  • Test data set & more info is at: DSpace 7 Performance Testing
  • A few areas that need work were called out:
    • Top Communities list on homepage takes over 2 seconds, see this table: https://cwilper.github.io/dspace-perftest/report/2019-06-04/7.0-preview-1/details-big#big-a-home-requests
    • Browse By Title with lots of larger bitstreams takes forever (26+ seconds), see this table: https://cwilper.github.io/dspace-perftest/report/2019-06-04/7.0-preview-1/details-browse
    • TODO: CREATE TICKETS for both of these specific performance issues, as they seem high priority.
  • Ideally, all REST queries should be <2 seconds (at slowest)
  • Andrea points out overlaps here with Projection discussions, see 

    Jira
    server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-3533

    • Projections would let the UI limit what info is returned per request.  This could speed up individual queries significantly, as often the UI doesn't need all metadata or all bitstreams... but currently all queries return a lot of embedded content, etc.
    • Need to revisit Projections in light of these results
  • Lots of suggestions for future performance testing areas (to enhance future data sets, testing points)
    • Testing performance from an SEO perspective (tests that act as a web crawler)
    • Testing performance of Entities (e.g. an article with many authors, or an person with many articles).  Paulo mentioned he has some real life data that could be used here
  • Additional suggestions should be added to Wiki page at DSpace 7 Performance Testing
• Laura briefly overviewed her design proposal for Community pages:
  •  See: Community page mockups
  • Designs were based on local user feedback at NYU
  • Discussion here was limited (as first topic ran long).  However, all are encouraged to bring these designs back to your institution for feedback/analysis.  Also looking for additional "Design objectives" (based on other local user testing).
  • REVISIT in meeting on August 1 (in two weeks, because Laura is out next week).  This topic will be first on the agenda that week.