Pinpoint: Service performance compression test,QPS reduce 90% ! help !!!

Created on 21 Jun 2017  Â·  5Comments  Â·  Source: pinpoint-apm/pinpoint

Description

My Tomcat service mainly involves Redis and Gson;

When not use Pinpint , the QPS is about 2000 ; Each request consumes about 200ms;

When use Pinpint ,the QPS is about 190 ; Each request consumes about 6200ms;

I saw the call_tree,ping() method costed about 1300ms;

Environment

redis : 2.6

help wanted stale

Most helpful comment

Check your log4.xml settings.

  • $PINPOINT_DIR/lib/log4.xml

All 5 comments

Check your log4.xml settings.

  • $PINPOINT_DIR/lib/log4.xml

Perfect!!! Your answer has solved my problem。I change the log level to ERROR, the project works near normally.
Just now I wrote a new test Demo , And the Demo is vary simple, just get a String from redis and transform it to a Object; when not use PP ,the QPS is about 19000 . when use PP ,the QPS is about 14000;
Would you give me some advice on how to minimize performance loss?
Thank you very much!!! @emeroad

There is a trade-off between performance and data precision.
If performance is more important than data precision, Low sample rate is recommended.

$PINPOINT_DIR/pinpoint.config

    # 1 out of n transactions will be sampled where n is the rate. (20: 5%)
    profiler.sampling.rate=20 

really usefull.

This issue/proposal has been automatically marked as stale because it hasn't had any recent activity. It will automatically be closed if no further activity occurs for 20days. If you think this should still be open, or the problem still persists, just pop a reply in the comments and one of the maintainers will (try!) to follow up. Thank you for your interest and contribution to the Pinpoint Community.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

CHENTIANHAO123 picture CHENTIANHAO123  Â·  4Comments

harissutanrafiq picture harissutanrafiq  Â·  5Comments

ing-arriola picture ing-arriola  Â·  4Comments

xulongju picture xulongju  Â·  3Comments

VidushaZ picture VidushaZ  Â·  6Comments