# Performance monitoring for nameko services

**URL:** <https://discourse.nameko.io/t/performance-monitoring-for-nameko-services/144>\
**Category:** googlegroup\
**Created:** [August 22, 2016, 10:13pm UTC](https://discourse.nameko.io/t/performance-monitoring-for-nameko-services/144 "2016-08-22T22:13:53Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jesse\_Pollak](https://avatars.discourse-cdn.com/v4/letter/j/b5a626/32.png) [@Jesse\_Pollak](https://discourse.nameko.io/u/Jesse_Pollak)\
**Post date:** [August 22, 2016, 10:13pm UTC](https://discourse.nameko.io/t/performance-monitoring-for-nameko-services/144/1 "2016-08-22T22:13:53Z")

</div>

Hi, we're in the process of re-evaluating whether it makes sense to keep  
paying our big New Relic subscription. We've been using nameko more and  
more, but haven't yet done any serious performance monitoring, so it's a  
big of an unknown when we're considering how it will interact with New  
Relic.

How are people doing performance monitoring for nameko? Anyone using New  
Relic or another similar tool?

Thanks!  
Jesse

---

<div class="post-metadata">

**Author:** ![mattbennett](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.nameko.io/mattbennett/32/13_2.png) [@mattbennett](https://discourse.nameko.io/u/mattbennett)\
**Post date:** [August 30, 2016, 1:45pm UTC](https://discourse.nameko.io/t/performance-monitoring-for-nameko-services/144/2 "2016-08-30T13:45:19Z")

</div>

I've never done any significant performance testing. We've profiled  
specific APIs before and found them to be spending a lot of time in the  
database driver or serializing JSON data. IIRC we did this by calling the  
service method locally though, so it didn't include much of nameko's  
internal mechanisms.

If you can justify continuing to use New Relic, I would love to see the  
results!

> **···**
>
> On Monday, August 22, 2016 at 11:13:53 PM UTC+1, Jesse Pollak wrote:
> 
> > Hi, we're in the process of re-evaluating whether it makes sense to keep  
> > paying our big New Relic subscription. We've been using nameko more and  
> > more, but haven't yet done any serious performance monitoring, so it's a  
> > big of an unknown when we're considering how it will interact with New  
> > Relic.
> > 
> > How are people doing performance monitoring for nameko? Anyone using New  
> > Relic or another similar tool?
> > 
> > Thanks!  
> > Jesse

---

<div class="post-metadata">

**Author:** ![Jesse\_Pollak](https://avatars.discourse-cdn.com/v4/letter/j/b5a626/32.png) [@Jesse\_Pollak](https://discourse.nameko.io/u/Jesse_Pollak)\
**Post date:** [August 30, 2016, 3:42pm UTC](https://discourse.nameko.io/t/performance-monitoring-for-nameko-services/144/3 "2016-08-30T15:42:27Z")

</div>

Good to know — I'll keep you updated!

> **···**
>
> On Tuesday, August 30, 2016 at 6:45:20 AM UTC-7, Matt Yule-Bennett wrote:
> 
> > I've never done any significant performance testing. We've profiled  
> > specific APIs before and found them to be spending a lot of time in the  
> > database driver or serializing JSON data. IIRC we did this by calling the  
> > service method locally though, so it didn't include much of nameko's  
> > internal mechanisms.
> > 
> > If you can justify continuing to use New Relic, I would love to see the  
> > results!
> > 
> > On Monday, August 22, 2016 at 11:13:53 PM UTC+1, Jesse Pollak wrote:
> > 
> > > Hi, we're in the process of re-evaluating whether it makes sense to keep  
> > > paying our big New Relic subscription. We've been using nameko more and  
> > > more, but haven't yet done any serious performance monitoring, so it's a  
> > > big of an unknown when we're considering how it will interact with New  
> > > Relic.
> > > 
> > > How are people doing performance monitoring for nameko? Anyone using New  
> > > Relic or another similar tool?
> > > 
> > > Thanks!  
> > > Jesse

---

<div class="post-metadata">

**Author:** ![Andryw\_Neo](https://avatars.discourse-cdn.com/v4/letter/a/ecc23a/32.png) [@Andryw\_Neo](https://discourse.nameko.io/u/Andryw_Neo)\
**Post date:** [December 7, 2016, 8:02pm UTC](https://discourse.nameko.io/t/performance-monitoring-for-nameko-services/144/4 "2016-12-07T20:02:36Z")

</div>

Hello everyone.  
How did you use nameko + newrelic? What were the commands you used?

> **···**
>
> On Tuesday, August 30, 2016 at 12:42:27 PM UTC-3, Jesse Pollak wrote:
> 
> > Good to know — I'll keep you updated!
> > 
> > On Tuesday, August 30, 2016 at 6:45:20 AM UTC-7, Matt Yule-Bennett wrote:
> > 
> > > I've never done any significant performance testing. We've profiled  
> > > specific APIs before and found them to be spending a lot of time in the  
> > > database driver or serializing JSON data. IIRC we did this by calling the  
> > > service method locally though, so it didn't include much of nameko's  
> > > internal mechanisms.
> > > 
> > > If you can justify continuing to use New Relic, I would love to see the  
> > > results!
> > > 
> > > On Monday, August 22, 2016 at 11:13:53 PM UTC+1, Jesse Pollak wrote:
> > > 
> > > > Hi, we're in the process of re-evaluating whether it makes sense to keep  
> > > > paying our big New Relic subscription. We've been using nameko more and  
> > > > more, but haven't yet done any serious performance monitoring, so it's a  
> > > > big of an unknown when we're considering how it will interact with New  
> > > > Relic.
> > > > 
> > > > How are people doing performance monitoring for nameko? Anyone using New  
> > > > Relic or another similar tool?
> > > > 
> > > > Thanks!  
> > > > Jesse

---

<div class="post-metadata">

**Author:** ![Simone\_Pontiggia](https://avatars.discourse-cdn.com/v4/letter/s/a8b319/32.png) [@Simone\_Pontiggia](https://discourse.nameko.io/u/Simone_Pontiggia)\
**Post date:** [March 11, 2017, 2:08am UTC](https://discourse.nameko.io/t/performance-monitoring-for-nameko-services/144/5 "2017-03-11T02:08:00Z")

</div>

I'll use newrelic this way:

in the dockerfile

# install newrelic agent  
RUN pip install newrelic  
ADD newrelic.ini /opt/service/newrelic.ini

and this on the method I want to profile

@newrelic.agent.background\_task()

Pretty simple and self building.

> **···**
>
> On Wednesday, 7 December 2016 12:02:36 UTC-8, andry...@gmail.com wrote:
> 
> > Hello everyone.  
> > How did you use nameko + newrelic? What were the commands you used?
> > 
> > On Tuesday, August 30, 2016 at 12:42:27 PM UTC-3, Jesse Pollak wrote:
> > 
> > > Good to know — I'll keep you updated!
> > > 
> > > On Tuesday, August 30, 2016 at 6:45:20 AM UTC-7, Matt Yule-Bennett wrote:
> > > 
> > > > I've never done any significant performance testing. We've profiled  
> > > > specific APIs before and found them to be spending a lot of time in the  
> > > > database driver or serializing JSON data. IIRC we did this by calling the  
> > > > service method locally though, so it didn't include much of nameko's  
> > > > internal mechanisms.
> > > > 
> > > > If you can justify continuing to use New Relic, I would love to see the  
> > > > results!
> > > > 
> > > > On Monday, August 22, 2016 at 11:13:53 PM UTC+1, Jesse Pollak wrote:
> > > > 
> > > > > Hi, we're in the process of re-evaluating whether it makes sense to  
> > > > > keep paying our big New Relic subscription. We've been using nameko more  
> > > > > and more, but haven't yet done any serious performance monitoring, so it's  
> > > > > a big of an unknown when we're considering how it will interact with New  
> > > > > Relic.
> > > > > 
> > > > > How are people doing performance monitoring for nameko? Anyone using  
> > > > > New Relic or another similar tool?
> > > > > 
> > > > > Thanks!  
> > > > > Jesse