Estimated compute
Use synchronized delivery facts to estimate how much compute time builds consumed.
Product capability · compute context
Estimate Xcode Cloud compute usage and understand CI performance.
Tazuki turns synchronized Xcode Cloud delivery facts into an estimated view of compute usage and CI performance, so time spent in builds has useful project context.
See how it worksWhat it is
An estimated usage view built from synchronized Xcode Cloud data.
Tazuki can estimate compute time from synchronized Steps and organize it by day, project, and action. It also keeps completed builds, active builds, queue time, execution time, end-to-end time, and parallelism context nearby.
At a glance
The useful shape of this capability.
Breakdowns
Read usage by day, project, and action when the source data provides those dimensions.
CI performance
Compare queue, execution, end-to-end, and parallelism context beside usage.
From synchronized Steps
Estimate Xcode Cloud compute usage from synchronized build steps.
Usage is not a number Tazuki invents in isolation. It is derived from synchronized Xcode Cloud delivery facts, including Steps, so the estimate can be read beside the builds that produced it.
- Estimated compute from synchronized Steps
- Completed build count
- Active build count
By context
Break down compute time by day, project, and action.
A total becomes more useful when it can be placed in a project, action, or day. Tazuki gives the estimate several practical slices without presenting it as a billing ledger.
- Daily usage
- Project usage
- Action usage
Performance around usage
Compare queue time, execution time, end-to-end time, and parallelism.
Queue time, execution time, end-to-end time, and parallelism describe different parts of the delivery experience. Tazuki keeps them close so a compute estimate has operational context.
- Queue time
- Execution and end-to-end time
- Parallelism ratio
A useful boundary
Usage is an estimate, not Apple billing.
Tazuki Usage is estimated from synchronized Xcode Cloud data. It should not be read as official billing usage, an exact Apple invoice, or a guaranteed total for every source-side event.
- No official billing authority
- No exact Apple billing guarantee
- No promise of complete data when synchronization is incomplete
Questions, answered
A capability with clear edges.
How can I track Xcode Cloud compute hours?
Apple reports Xcode Cloud subscription usage in compute hours. Tazuki independently estimates compute time from the synchronized build steps available to it, so its Usage view should not be treated as Apple’s official billing total.
Are Xcode Cloud build minutes and compute hours the same as build duration?
No. Wall-clock build duration and compute usage are different concepts because build actions can execute in parallel. Tazuki keeps usage estimates and CI performance context separate from the Build Duration view.
Is Tazuki Usage official Xcode Cloud billing?
No. Tazuki Usage is estimated from synchronized Xcode Cloud data. It is not an Apple billing authority or a guaranteed billing total.
What can the Usage view show?
It can show estimated compute usage, completed and active build counts, daily, project, and action usage, plus queue, execution, end-to-end, and parallelism context when the synchronized data supports it.
Why does the estimate depend on synchronized data?
Tazuki derives the estimate from the Steps and other delivery facts it can synchronize. The result is only as complete as the source data available to the app.
Tazuki · macOS 14+
Keep the useful context close.
Tazuki is available on the Mac App Store. Download it free and unlock remote synchronization with Pro.
Download on the Mac App Store