Difference between revisions of "SwiftHighCPU"
m (Text replace - "__NOTOC__" to "") |
|||
| Line 1: | Line 1: | ||
| − | + | ||
== Problem == | == Problem == | ||
In our testing Swift environment, we find that CPU utilization rate of Storage node often goes up to 100% even without any request. | In our testing Swift environment, we find that CPU utilization rate of Storage node often goes up to 100% even without any request. | ||
Latest revision as of 23:30, 17 February 2013
Problem
In our testing Swift environment, we find that CPU utilization rate of Storage node often goes up to 100% even without any request.
Verification
Testing environment
- Nodes: 5 x Dell R510
- CPU: Intel® Xeon® E5360
- Memory: 12GB
- Replica: 3
- No. of Objects: 150,000,000
- No. of Accounts: 120,000
- No. of Containers: 160,000
Audit
Each command run for only one time, and count their time usage:
- swift-account-auditor : 1.5m
- swift-account-replicator: 9.5m
- swift-container-auditor: 8.4m
- swift-container-replicator: 9.3m
- swift-container-updater: 19.0m
- swift-object-updater: 0.1 s
- swift-object-replicator: 10.5 hours
- swift-object-auditor: 48.3 hours
