I notice that in the Event detail page, all of the attendees are being
displayed. As a run progresses, more attendees will be added and the
number of rows that need to be retrieved and displayed will keep
increasing causing a performance degradation.
We ran into this issue with the PHP app and worked around it by limiting
the number of attendees displayed to 20. There is a JIRA filed to make
the attendee list pagable. This will improve the app but since it
doesn't affect the workload, it is a low priority to fix this JIRA.
In the Java runs I've done, I don't necessarily see this issue (which
manifests itself as increasing usr time and a potential drop in
throughput as the run progresses). But then my system isn't very busy.
It might be good if others checked their runs to see if they notice any
increase in db workload and/or drop in throughput.
Thanks
Shanti
