Carthage/Carthage

High CPU usage attributed to `carthage` when blocking on tasks

Open

#126 opened on Nov 21, 2014

View on GitHubContributor guide
 (3 comments) (0 reactions) (0 assignees)Swift (1,544 forks)batch import
bughelp wantedupdate

Repository metrics

Stars
 (15,179 stars)
PR merge metrics
 (PR metrics pending)

Description

During a long series of Git operations, carthage was spiking to > 200% CPU usage, despite the fact that most of the work was happening in git processes.

We may be unintentionally busy-waiting somewhere (perhaps because a task isn't quiet that should be?) or shelling out too frequently.

Contributor guide

Research direction
Profile the CPU usage to identify the busy waiting loop. Look for tasks that are supposed to be blocking but are polling or spinning. Inspect usage of DispatchGroup or semaphores in the codebase.
Tech stack
swift
Domain
cliperformance
Issue type
Performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
SwiftGitXcode
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45