Containerize the runtime events in a ring buffer.

[matttproud]

To enable someone to use this tool to observe event streams over
sliding windows of sample recency as well as prevent unbound growth of
observations, the list of observations has been wrapped in a ring
buffer of flag-specifiable size. This has been a tremendous help
in visualizing events from particularly garbage collector-active
servers.

[davecheney]

Thanks. I'll take a look tonight
On 13 Jul 2014 23:01, "Matt T. Proud" notifications@github.com wrote:

To enable someone to use this tool to observe event streams over
sliding windows of sample recency as well as prevent unbound growth of
observations, the list of observations has been wrapped in a ring
buffer of flag-specifiable size. This has been a tremendous help
in visualizing events from particularly garbage collector-active

servers.

You can merge this Pull Request by running

git pull https://github.com/matttproud/gcvis feature/ring-buffer-history

Or view, comment on, or merge it at:

#6
Commit Summary

• Containerize the runtime events in a ring buffer.

File Changes

• M main.go https://github.com/davecheney/gcvis/pull/6/files#diff-0
  (115)

Patch Links:

• https://github.com/davecheney/gcvis/pull/6.patch
• https://github.com/davecheney/gcvis/pull/6.diff

—
Reply to this email directly or view it on GitHub
#6.

[davecheney]

Hmm. Let me think about this. I'm not sure this pays for itself given we have the slider to zoom into a particular area of the trace.

[Dieterbe]

for cases like this, you could also just stream the values into something like graphite or influxdb and visualize with something like grafana.