This is not good: instead, the reviewIDs need to be cached. Until this can be implemented (<http://hackydev.ics.hawaii.edu:8080/browse/HACK-561>), I've taken hackyApp_Review out of the hackystat-UH configuration.
Cheers, Philip
I've been profiling Hackystat today, and discovered a big performance hit in
hackyApp_Review. When the reviewID selector is first invoked (i.e. when the page
containing it is retrieved for the first time), it reads in all review data that's ever
been sent to the system.
