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
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
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
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
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