Saving 13 Million Computational Minutes per Day with Flame Graphs
Netflix Technology Blog
512

G’day

This is a very interesting article on how you folks at Netflix have gone about identifying the culprit API/Package resulting in high CPU utilization. The initial part of the article is very informative but the crux of the article which deals with identifying the package is a little vague.

Could you explain how :

  1. You reprocessed the stack traces to collapse the repetitive framework calls
  2. How did you identify the “potential expensive” package?
  3. Filtered out the frames in each call stack until you reached a method calling this package.
Like what you read? Give sanjeed schamnad a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.