i will try to pay attention to this. i think dave is right that this is likely a more general study performance issue than getQueryDetails() specifically. I think the right thing to do is to follow up properly on the test server, but here are some symptoms I have seen to date on my laptop with the EHR study:

while in the query module schema browser, it is not uncommon for loading the study schema to timeout (meaning expanding the list of tables). Likewise for loading the info page on the participant or study data tables (not data itself).

i have noticed that if i try to load a very big table without any sort of filter, i can cause this slow behavior. for example, trying to load studydata, participant or assignment. i'm not sure how to properly kill one of these queries, but they seem to slow performance after not actually loading.


machine specs:
Running labkey checked out from from 10.1 branch.
postgres 8.4
Dell inspiron Core2duo T7500 2.2ghz
4gb RAM
win7 32-bit