mirror of
https://github.com/storytold/vectorcraft.git
synced 2026-10-24 09:46:59 -06:00
dotCooCoo
6928f422d3
perf --deep printed the memory at eight points of its run, and no row showed memory that the run took and freed between two readings. With --paths 2000, a release build on Windows printed 430 MB as its largest row, and the process's peak working set was 612 MB. On Windows the memory row after rendering the photos also printed its value 3 columns right of the others: its name is 55 characters, and the name column is 52 characters wide. The tracked row for the photos printed its value 2 columns right of the other tracked rows: its name is 54 characters, and their name column is 52 characters wide. In the budget table the handle and segment drag rows printed their values 1 and 2 columns right of the other rows: their names are 41 and 42 characters, and the name column is 40 characters wide. Each memory row now also gives the peak so far: the peak working set (PeakWorkingSetSize, from the same GetProcessMemoryInfo call) on Windows, and VmHWM from /proc/self/status on Linux. On macOS the rows give no peak. A new last row gives the memory after the SVG export and the save → open → save at the end of the run. The name columns of the memory rows, the tracked rows and the budget table are 56, 54 and 42 characters wide. The help says on which systems the rows give the peak. Docs: docs/target-app-parity.md.