jlfwong/speedscope

Format Support: concatenated output from many calls to jstack

Open

#173 opened on Oct 7, 2018

View on GitHub
 (3 comments) (0 reactions) (0 assignees)TypeScript (4,040 stars) (181 forks)batch import
charity donation bountyhelp wantedimport source

Description

Poor man's profiling of a JVM:

$ for i in `seq 1 300`;do jstack $(pgrep java) > $i.jstack;sleep 1;done;zip profile.zip *.jstack;rm *.jstack

...and then uploading profile.zip. I'm tired of opening up traffic for profiling to production and/or building lots of tooling around it. jstack (and shell) is always availalable.

Contributor guide

Tech stack
typescript
Domain
performancedata
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
TypeScriptspeedscope import architectureJVM stack trace format
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
First, examine speedscope's existing import system in the src/import/ directory to understand how other profile formats (e.g., Chrome trace) are parsed. Then, implement a new importer that reads a zip file containing multiple jstack outputs, extracts each file, parses the thread dumps, and concatenates them into a single profile. Test the new format by creating sample jstack outputs and verifying the viewer displays them correctly. Check issue comments for any additional maintainer guidance.