When we run the Profiler, the runtime of "select" type queries are dramatically understated. This is because the Profiler only counts the time of the "query", and doesn't include how long it took to "fetch" the result set.

In one of our test cases, we "tuned" the query so it only shows as running 82 ms in the Profiler. However, when we actually run this same query in JavaScript, the runtime is 10 seconds. This is a very slow query which our end users experience many times a day.

Is there a way to configure Profiler to be more realistic, and include the "fetch time" as well as the "query" time?

Currently, the Profiler seems to be of little us in finding slow queries. We have to find them using other means.

Thank you.