It seems like this happened after 684e20b99aa348133890f2203ade429bd211cc72 and 66c83387040e75c0471760ea96f4f7b434cf7584 landed. It may be that given the increased volume of data on Linux, adding the display version to our query was the straw that broke the camel's back. However, I'm a bit confused because it seems like Linux-based queries are completing in a reasonable amount of time on redash...
I'd like to start by logging the exact presto sql statement we're running to new relic, so we can more easily diagnose what's happening here. From there, we can try to tune things up.
wlach
commented
6 years ago
Some Linux release queries seem to not be completing, presumably because of the volume of data being returned? You can see what they are here:
https://data-missioncontrol.dev.mozaws.net/#/release/linux
It seems like this happened after 684e20b99aa348133890f2203ade429bd211cc72 and 66c83387040e75c0471760ea96f4f7b434cf7584 landed. It may be that given the increased volume of data on Linux, adding the display version to our query was the straw that broke the camel's back. However, I'm a bit confused because it seems like Linux-based queries are completing in a reasonable amount of time on redash...
I'd like to start by logging the exact presto sql statement we're running to new relic, so we can more easily diagnose what's happening here. From there, we can try to tune things up.