Getting the SongDetailView (with its long list of recordings) can often break from a performance perspective. Can we build a test harness that is easy to run that confirms that, after making changes, the API call still returns in a reasonable time/doesn't make exceptionally large numbers of DB queries?
Getting the SongDetailView (with its long list of recordings) can often break from a performance perspective. Can we build a test harness that is easy to run that confirms that, after making changes, the API call still returns in a reasonable time/doesn't make exceptionally large numbers of DB queries?