Skip to content
This repository has been archived by the owner on Aug 25, 2020. It is now read-only.

Newrelic-grape responsible for most of the response time? #14

Open
monfresh opened this issue Sep 26, 2013 · 2 comments
Open

Newrelic-grape responsible for most of the response time? #14

monfresh opened this issue Sep 26, 2013 · 2 comments

Comments

@monfresh
Copy link

I'm trying to figure out if I'm using this gem correctly or if I'm missing something that's not mentioned in the documentation. I installed the gem, making sure to place it after grape and newrelic_rpm, and when I drill down on an API call, it points to the newrelic-grape code as the source of the most time spent on the query. When I click on GET api-locations-:locations_id-nearby on this page: http://d.pr/i/hy7Z
it takes me here: http://d.pr/i/XsKg

Does that mean that the perform_action_with_newrelic_trace(trace_options) do block is what's taking up 162 out of 193ms?

I was expecting it to show me which part of the Grape API call is taking the most time.

@flyerhzm
Copy link
Member

@monfresh looks like most time are taken to send http get request.

@dmitry
Copy link

dmitry commented Sep 22, 2015

Could be closed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants