4.0 performance

[eaquigley]

---

Author Name: Philip Durbin (@pdurbin)
Original Redmine Issue: 3593, https://redmine.hmdc.harvard.edu/issues/3593
Original Date: 2014-02-26
Original Assignee: Philip Durbin

---

The goal is page load speed of 1000 milliseconds or less for navigation pages given the following hardware specs: FIXME.

[This ticket is a stub. http://www.codinghorror.com/blog/2011/06/performance-is-a-feature.html :) ]

Resources:

• http://developers.google.com/speed/pagespeed/insights/?url=dataverse-demo.iq.harvard.edu
• http://www.webpagetest.org

---

Related issue(s): #50, #182
Redmine related issue(s): 3457, 3594

---

[raprasad]

build server slow down (inadvertent)

Using the native API, I ran a test script to add 600+ actual dataverse names, affiliations, and aliases.

They were all added under:

• dataverse: root
• apikey/user: pete

This slowed the initial front page load time to 1:26 and “paging” through the dataverse names takes over 1 min per click.

Whether or not a user is logged in, the front page load time is the same.

• Not logged in: 16 dataverses, ~80 second load time
• Logged in as Pete: 600+ dataverses, ~80 second load time

Clicking on an actual dataverse name works “instantly”—it’s only the listing page that takes time.

[pdurbin]

Using the native API, I ran a test script to add 600+ actual dataverse names, affiliations, and aliases

@raprasad this sounds like a very useful script. Can you please commit it if you haven't already?

[pdurbin]

This slowed the initial front page load time to 1:26 and “paging” through the dataverse names takes over 1 min per click.

I opened #785 for this based on my local testing with the script @raprasad just added to https://github.com/IQSS/dv-api-test . Thanks, for finding this performance issue! We'll fix it in that ticket.

[esotiri]

home page performance related issue #800
featured dateverses on save #801

[raprasad]

Please examine queries at a page-by-page level for performance.

If you want to see the queries generated for an individual Dataverse page, make the following changes:

• Edit the persistence .xml file. (I edited this outside of NetBeans to see the actual XML)
• Add this line within the <properties> tags:
  <property name="eclipselink.logging.level.sql" value="FINE"/>
• NetBeans should redeploy and add SQL statements