Optimizations

[danielBingham]

Story Description

What are we trying to accomplish in plain english?

We very intentionally didn't allow ourselves to pre-maturely optimize. As a result, the application is rather slow in parts - particularly when loading the paper lists. GET /papers is a big join query and it returns a lot of data we don't need on the lists. Calling that query for everything is very slow. Half a second even when we don't have very many papers in the database yet. We could easily write a much, much simpler query to get everything we need for the lists. There's probably a lot of other optimizations beside we should consider before we go to closed beta. So lets do an optimization pass to ensure things are moving reasonably efficiently.

Acceptance Criteria

At what point is this story considered "done"?

• We have optimized the query used by the paper lists.
• We have optimized the way comment threads are handled on the review screen.

Dependencies

What stories does this one depend on? What do we need to do first before we can call this one done?