Very Sleepy: CPU samples and native stacks
Target PID, symbols, inclusive/exclusive and incomplete-capture diagnosis.
Very Sleepy is a Windows CPU sampling profiler for locating expensive native stacks. It measures no GPU render passes and does not replace a managed profiler for C# logic. Prepare the binary/matching symbols using the shared guide.
Capture the intended process
- Launch the Reckfell project with explicit
--pathto itsproject.reckfelldirectory; add--editorfor editor work. Confirm the target action reproduces first. - Select the target PID in Very Sleepy. Project Manager and a launched game may be different processes. For short-lived startup, use profiler launch rather than late attach.
- Capture the relevant threads, repeat the action and finish with Stop. Save a
.sleepysession alongside launch settings. The official wiki describes launching/saving.
Read the results
Compare Inclusive/Exclusive in Functions, then inspect Call Stacks and callers. Inclusive includes callees; summing all inclusive rows does not give independent frame costs. Start unfiltered before selecting your executable/native DLL by Module. A filter hides displayed work without proving zero driver/OS cost. See User Interface for these views.
If functions appear as addresses, check symbols for that exact build and the resolving log. Equal source filenames do not validate another revision's lines. For saved sessions, see Late Symbol Resolution; MinGW symbols need their matching workflow.
Unhelpful captures
| Symptom | Check |
|---|---|
| Mostly idle/Project Manager | Correct PID and actual game/editor target |
| Target action missing | Capture duration, selected threads and reproducibility |
| Addresses/unknown only | Binary/symbol match, search paths and toolchain symbol format |
| High driver/system percentage | Inspect the complete capture; CPU sampling does not time GPU passes |
Repeat equal actions and compare absolute costs. A lower function percentage alone establishes no speedup.
Verification limits
Procedure reviewed against the official wiki and Reckfell 1.0.0 options. Local execution covered CLI targeting and the first --quit iteration only. Very Sleepy capture/attach, GUI, symbols and performance results remain untested. Engine source, Runtime and SDK unchanged.