PerformanceDaddy

A local Mac performance investigator for background apps, helpers and developer workloads, with measured evidence and reviewed actions.

Maker note

Why I made this.

I am building a local Mac performance investigator that makes process, port and slowdown evidence easier to review.

Product contract

PerformanceDaddy helps developers inspect local processes, ports and measured slowdown signals before taking action.

For: Developers running local servers, coding agents and other moving parts on a Mac.
Outcome: Find the process or port evidence behind a slowdown and choose the next check deliberately.
How: A native local Mac app records bounded CPU, memory, thermal, process and socket observations with reviewed stop controls.
Proof: The public signed Sparkle feed and download serve notarized 0.2.3 build8 with matching DMG bytes. An isolated build3-to-5 Sparkle update and native journey were observed; build8 has not been installed for a new journey.
Next action: Read the public landing and use the current GitHub release for a Mac install; review measured evidence before acting on a diagnosis.

Public anatomy

Maintained evidence

Public destinations and repository evidence, when this project publishes them.

Repository publication

Public issues become a browsable, read-only record here. Open the source issue to comment, react, or follow the work.

The embedded reader is loading or unavailable. Read the issues in the source repository.

Every fact here comes from the project’s reviewed public record. Private work and operational controls stay private.