What version of Grails? Java? OS?

Grails 3.1.0 - 3.1.5
Java 8u72
OS Red Hat Enterprise Linux Server release 7.2 (Maipo)

@ColinHarrington Have any spare yourkit licenses laying around!? 😆

Closing until we can isolate and pinpoint.

I am seeing the same problem as well. We are using New Relic to track performance and apparently our biggest bottle neck is GrailsControllerUrlMappingInfo.

We have around 50 entries in our UrlMapping. An example of such an entry will be:

group("/api") {
            "/deployments"(controller: "deployments", action: "list", method: "get")
}

An example on github that reproduces the issue would be good

that particular class doesn't do much, so it would have to be something else

https://github.com/grails/grails-core/blob/master/grails-web-url-mappings/src/main/groovy/org/grails/web/mapping/mvc/GrailsControllerUrlMappingInfo.groovy

@sergiodelamoshoptimix We assume this an issue with how New Relic instruments the code. I think the GrailsControllerUrlMappingInfo.groovy class is involded in every request to resolve the actual class that does the work and the New Relic Instrumentation stops at this class or thinks this is the actual class that is running when it appears that the class actually is delegating the work which NR must not like. We are still looking at other tools to see if we can hammer out actual perf problems.

@graemerocher @ctoestreich Thanks for the explanation. I think you are right and New Relic is attributing most of the executing time to GrailsControllerUrlMappingInfo while the time is actually spent in Controllers and Services.

@sdelamo did you report the issue to NewRelic?

It looks like they officially support 1.x and 2.x version, but maybe not yet 3.x?
https://newrelic.com/java/grails

@sdelamo This behavior is similar to what we saw before New Relic supported Grails 1.x or 2.x. I would guess that they have a little bit of work to do to support Grails 3

I've requested that they do the same for Grails 3
Feature Request

One thing that helps is to turn off Auto Naming for transactions in your New Relic account.

Reference

Disabling component-based naming

For some applications, you may want to disable component-based transaction naming. Set this value in your newrelic.yml file:
enable_auto_transaction_naming: false
Unless you implement API calls to name your transactions, disabling auto-transaction naming is very likely to cause Metric grouping issues.

Per their docs you may have to add back in the group mapping url stuff. We got burned on our /search endpoint and had to add a /search/* mapping to group with the auto naming off.

Hi @ctoestreich Thanks for suggesting the disabling component-based naming. It helps indeed.

@benorama , I have upvoted the @ColinHarrington feature request. Lets see if they bring Grails 3 support on.