Difference between revisions of "SwiftHighCPU"
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
| − | == | + | == 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. | ||
| + | |||
| + | == 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 | ||
Revision as of 15:07, 16 April 2012
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
