You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by GitBox <gi...@apache.org> on 2021/04/07 12:25:22 UTC

[GitHub] [skywalking] wu-sheng commented on issue #6703: The Java Agent may cause frequent GC or OOM in extreme scenarios

wu-sheng commented on issue #6703:
URL: https://github.com/apache/skywalking/issues/6703#issuecomment-814871986


   Let's talk about this from a different perspective.
   > So how SkyWalking Java Agent can do in such extreme scenarios? Because the application availability is very important, all of us won't hope the APM instrument occupies a lot of memory.
   
   SkyWalking agent would provide a unlimited size of spans per segment, you could find the configuration in the agent, it would be 300 spans per segment mostly.
   
   > I wonder why put the segment in the ring buffer, could we put the span? I don't familiar with the Segment design purpose.
   
   If you don't have this concept, you can't tell the links(metrics) between entry span and exit spans, such as one day, we may need N database operations per HTTP request. Also, your codes actually cache much more data than we did for tracing the context.
   **Unless, like in your case**, I would say you must put the parameter collection by yourself. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org