13.2 Labkey.Query.selectRows latency

LabKey Support Forum
13.2 Labkey.Query.selectRows latency Anthony Corbett  2013-10-15 16:29
Status: Closed
 
I'm doing some testing for upgrading our servers to 13.2 and I'm noticing an increase in latency for HTTP requests using the JavaScript Query.selectRows method. Attached is a image showing the comparison between 13.1 (our production server) and 13.2 (our staging server) running the same query against the same dataset and same row. It takes 288ms on 13.1 and on 13.2 it takes 6.25 seconds. Both the wait time and the receiving time are very different between the two HTTP requests.

Our staging server database is a mirror of the production database, the only thing that has changed is the labkey version. The hardware is different but not drastically different. The tomcat and postgres configurations are identical.

I did some ping tests and those averaged out to the same latency. I then did trace routes between my local machine and both production and staging and the number of hops and latency between hops is the same.

This different in latency is showing up regardless of Study or dataset within the study.

I didn't try 13.1 and 13.2 on my local box to see if there is a difference (I'll do that tomorrow morning). However, I'm wondering if this can be reproduced by anyone else? Or is there something that needs to be configured on our side when upgrading to 13.2?

Thanks in advance,

Anthony Corbett
 
 
jeckels responded:  2013-10-15 17:57
Hi Anthony,

What target queries are you hitting with the API? It sounds like study datasets?

Do you see similar perf differences on other, unrelated queries, like core.containers or exp.runs?

Thanks,
Josh
 
Anthony Corbett responded:  2013-10-16 09:25
Josh,

Yes, these are study datasets. I ran API calls against core.containers and exp.runs and they don't have the same latency.

-
Anthony