4 measured workloads · Node.js · Apple M4 Pro
Typical processing
6.00 µs
Busier blocks
6.67 µs
Share of the test budget
0.5%
50 ms multitap · feedback 0.2 · 96 kHz · 1.333 ms available per block in this test.
Processing time in µs · lower means less work
Timing varied between repeated tests. Treat this case as a guide.
Remaining energy · dB
| Sample rate · kHz | Workload | Typical · µs | Busier blocks · µs | Test budget used | Observations |
|---|---|---|---|---|---|
| 48 | 6.04 | 6.46 | 0.2% | Timing varies | |
| 48 | 6.04 | 6.92 | 0.3% | Timing varies | |
| 96 | 6.00 | 6.54 | 0.5% | Timing varies · Some blocks exceeded the budget | |
| 96 | 6.00 | 6.67 | 0.5% | Timing varies |
Times are per 128-frame audio block. Test budget used divides the p95 time by the block period at that case’s sample rate. Machine and runtime are shared.
Node.js · Apple M4 Pro · 48 / 96 kHz · 128 frames per block · 3 repeated tests ·
Typical summarizes the middle measured block times. Busier blocks summarizes the time that 95% of blocks completed within in each repeat. These figures measure DSP processing; application scheduling, loading samples and device output require separate checks. Memory and signal probes run separately from the timing loop.