performance-analysis
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChinesePerformance Analysis Skill
性能分析Skill
Comprehensive performance analysis suite for identifying bottlenecks, profiling swarm operations, generating detailed reports, and providing actionable optimization recommendations.
针对Claude Flow集群的全面性能分析套件,可用于识别瓶颈、剖析集群操作、生成详细报告并提供可落地的优化建议。
Overview
概述
This skill consolidates all performance analysis capabilities:
- Bottleneck Detection: Identify performance bottlenecks across communication, processing, memory, and network
- Performance Profiling: Real-time monitoring and historical analysis of swarm operations
- Report Generation: Create comprehensive performance reports in multiple formats
- Optimization Recommendations: AI-powered suggestions for improving performance
该Skill整合了所有性能分析能力:
- 瓶颈检测:识别通信、处理、内存和网络层面的性能瓶颈
- 性能剖析:对集群操作进行实时监控与历史分析
- 报告生成:以多种格式创建全面的性能报告
- 优化建议:基于AI生成的性能提升建议
Quick Start
快速开始
Basic Bottleneck Detection
基础瓶颈检测
bash
npx claude-flow bottleneck detectbash
npx claude-flow bottleneck detectGenerate Performance Report
生成性能报告
bash
npx claude-flow analysis performance-report --format html --include-metricsbash
npx claude-flow analysis performance-report --format html --include-metricsAnalyze and Auto-Fix
分析并自动修复
bash
npx claude-flow bottleneck detect --fix --threshold 15bash
npx claude-flow bottleneck detect --fix --threshold 15Core Capabilities
核心能力
1. Bottleneck Detection
1. 瓶颈检测
Command Syntax
命令语法
bash
npx claude-flow bottleneck detect [options]bash
npx claude-flow bottleneck detect [options]Options
可选参数
- - Analyze specific swarm (default: current)
--swarm-id, -s <id> - - Analysis period: 1h, 24h, 7d, all (default: 1h)
--time-range, -t <range> - - Bottleneck threshold percentage (default: 20)
--threshold <percent> - - Export analysis to file
--export, -e <file> - - Apply automatic optimizations
--fix
- - 分析指定集群(默认:当前集群)
--swarm-id, -s <id> - - 分析周期:1h、24h、7d、all(默认:1h)
--time-range, -t <range> - - 瓶颈阈值百分比(默认:20)
--threshold <percent> - - 将分析结果导出至文件
--export, -e <file> - - 应用自动优化
--fix
Usage Examples
使用示例
bash
undefinedbash
undefinedBasic detection for current swarm
对当前集群进行基础检测
npx claude-flow bottleneck detect
npx claude-flow bottleneck detect
Analyze specific swarm over 24 hours
分析指定集群过去24小时的情况
npx claude-flow bottleneck detect --swarm-id swarm-123 -t 24h
npx claude-flow bottleneck detect --swarm-id swarm-123 -t 24h
Export detailed analysis
导出详细分析结果
npx claude-flow bottleneck detect -t 24h -e bottlenecks.json
npx claude-flow bottleneck detect -t 24h -e bottlenecks.json
Auto-fix detected issues
自动修复检测到的问题
npx claude-flow bottleneck detect --fix --threshold 15
npx claude-flow bottleneck detect --fix --threshold 15
Low threshold for sensitive detection
低阈值敏感检测
npx claude-flow bottleneck detect --threshold 10 --export critical-issues.json
undefinednpx claude-flow bottleneck detect --threshold 10 --export critical-issues.json
undefinedMetrics Analyzed
分析指标
Communication Bottlenecks:
- Message queue delays
- Agent response times
- Coordination overhead
- Memory access patterns
- Inter-agent communication latency
Processing Bottlenecks:
- Task completion times
- Agent utilization rates
- Parallel execution efficiency
- Resource contention
- CPU$memory usage patterns
Memory Bottlenecks:
- Cache hit rates
- Memory access patterns
- Storage I/O performance
- Neural pattern loading times
- Memory allocation efficiency
Network Bottlenecks:
- API call latency
- MCP communication delays
- External service timeouts
- Concurrent request limits
- Network throughput issues
通信瓶颈:
- 消息队列延迟
- Agent响应时间
- 协调开销
- 内存访问模式
- Agent间通信延迟
处理瓶颈:
- 任务完成时间
- Agent利用率
- 并行执行效率
- 资源竞争
- CPU/内存使用模式
内存瓶颈:
- 缓存命中率
- 内存访问模式
- 存储I/O性能
- 神经模式加载时间
- 内存分配效率
网络瓶颈:
- API调用延迟
- MCP通信延迟
- 外部服务超时
- 并发请求限制
- 网络吞吐量问题
Output Format
输出格式
🔍 Bottleneck Analysis Report
━━━━━━━━━━━━━━━━━━━━━━━━━━━
📊 Summary
├── Time Range: Last 1 hour
├── Agents Analyzed: 6
├── Tasks Processed: 42
└── Critical Issues: 2
🚨 Critical Bottlenecks
1. Agent Communication (35% impact)
└── coordinator → coder-1 messages delayed by 2.3s avg
2. Memory Access (28% impact)
└── Neural pattern loading taking 1.8s per access
⚠️ Warning Bottlenecks
1. Task Queue (18% impact)
└── 5 tasks waiting > 10s for assignment
💡 Recommendations
1. Switch to hierarchical topology (est. 40% improvement)
2. Enable memory caching (est. 25% improvement)
3. Increase agent concurrency to 8 (est. 20% improvement)
✅ Quick Fixes Available
Run with --fix to apply:
- Enable smart caching
- Optimize message routing
- Adjust agent priorities🔍 瓶颈分析报告
━━━━━━━━━━━━━━━━━━━━━━━━━━━
📊 摘要
├── 时间范围:过去1小时
├── 分析Agent数量:6
├── 处理任务数量:42
└── 关键问题:2
🚨 严重瓶颈
1. Agent通信(影响占比35%)
└── coordinator → coder-1消息平均延迟2.3秒
2. 内存访问(影响占比28%)
└── 神经模式加载每次访问耗时1.8秒
⚠️ 警告瓶颈
1. 任务队列(影响占比18%)
└── 5个任务等待分配超过10秒
💡 优化建议
1. 切换至分层拓扑结构(预计提升40%)
2. 启用内存缓存(预计提升25%)
3. 将Agent并发数增加至8(预计提升20%)
✅ 可用快速修复
添加--fix参数运行以应用:
- 启用智能缓存
- 优化消息路由
- 调整Agent优先级2. Performance Profiling
2. 性能剖析
Real-time Detection
实时检测
Automatic analysis during task execution:
- Execution time vs. complexity
- Agent utilization rates
- Resource constraints
- Operation patterns
任务执行期间自动分析:
- 执行时间与复杂度对比
- Agent利用率
- 资源限制
- 操作模式
Common Bottleneck Patterns
常见瓶颈模式
Time Bottlenecks:
- Tasks taking > 5 minutes
- Sequential operations that could parallelize
- Redundant file operations
- Inefficient algorithm implementations
Coordination Bottlenecks:
- Single agent for complex tasks
- Unbalanced agent workloads
- Poor topology selection
- Excessive synchronization points
Resource Bottlenecks:
- High operation count (> 100)
- Memory constraints
- I/O limitations
- Thread pool saturation
时间瓶颈:
- 任务耗时超过5分钟
- 可并行化的串行操作
- 冗余文件操作
- 低效算法实现
协调瓶颈:
- 单个Agent处理复杂任务
- Agent工作负载不均衡
- 拓扑选择不当
- 过多同步点
资源瓶颈:
- 操作次数过多(>100)
- 内存限制
- I/O限制
- 线程池饱和
MCP Integration
MCP集成
javascript
// Check for bottlenecks in Claude Code
mcp__claude-flow__bottleneck_detect({
timeRange: "1h",
threshold: 20,
autoFix: false
})
// Get detailed task results with bottleneck analysis
mcp__claude-flow__task_results({
taskId: "task-123",
format: "detailed"
})Result Format:
json
{
"bottlenecks": [
{
"type": "coordination",
"severity": "high",
"description": "Single agent used for complex task",
"recommendation": "Spawn specialized agents for parallel work",
"impact": "35%",
"affectedComponents": ["coordinator", "coder-1"]
}
],
"improvements": [
{
"area": "execution_time",
"suggestion": "Use parallel task execution",
"expectedImprovement": "30-50% time reduction",
"implementationSteps": [
"Split task into smaller units",
"Spawn 3-4 specialized agents",
"Use mesh topology for coordination"
]
}
],
"metrics": {
"avgExecutionTime": "142s",
"agentUtilization": "67%",
"cacheHitRate": "82%",
"parallelizationFactor": 1.2
}
}javascript
// 在Claude Code中检查瓶颈
mcp__claude-flow__bottleneck_detect({
timeRange: "1h",
threshold: 20,
autoFix: false
})
// 获取包含瓶颈分析的详细任务结果
mcp__claude-flow__task_results({
taskId: "task-123",
format: "detailed"
})结果格式:
json
{
"bottlenecks": [
{
"type": "coordination",
"severity": "high",
"description": "Single agent used for complex task",
"recommendation": "Spawn specialized agents for parallel work",
"impact": "35%",
"affectedComponents": ["coordinator", "coder-1"]
}
],
"improvements": [
{
"area": "execution_time",
"suggestion": "Use parallel task execution",
"expectedImprovement": "30-50% time reduction",
"implementationSteps": [
"Split task into smaller units",
"Spawn 3-4 specialized agents",
"Use mesh topology for coordination"
]
}
],
"metrics": {
"avgExecutionTime": "142s",
"agentUtilization": "67%",
"cacheHitRate": "82%",
"parallelizationFactor": 1.2
}
}3. Report Generation
3. 报告生成
Command Syntax
命令语法
bash
npx claude-flow analysis performance-report [options]bash
npx claude-flow analysis performance-report [options]Options
可选参数
- - Report format: json, html, markdown (default: markdown)
--format <type> - - Include detailed metrics and charts
--include-metrics - - Compare with previous swarm
--compare <id> - - Analysis period: 1h, 24h, 7d, 30d, all
--time-range <range> - - Output file path
--output <file> - - Comma-separated sections to include
--sections <list>
- - 报告格式:json、html、markdown(默认:markdown)
--format <type> - - 包含详细指标与图表
--include-metrics - - 与历史集群进行对比
--compare <id> - - 分析周期:1h、24h、7d、30d、all
--time-range <range> - - 输出文件路径
--output <file> - - 需包含的以逗号分隔的章节列表
--sections <list>
Report Sections
报告章节
-
Executive Summary
- Overall performance score
- Key metrics overview
- Critical findings
-
Swarm Overview
- Topology configuration
- Agent distribution
- Task statistics
-
Performance Metrics
- Execution times
- Throughput analysis
- Resource utilization
- Latency breakdown
-
Bottleneck Analysis
- Identified bottlenecks
- Impact assessment
- Optimization priorities
-
Comparative Analysis (when --compare used)
- Performance trends
- Improvement metrics
- Regression detection
-
Recommendations
- Prioritized action items
- Expected improvements
- Implementation guidance
-
执行摘要
- 整体性能得分
- 关键指标概览
- 重要发现
-
集群概览
- 拓扑配置
- Agent分布
- 任务统计
-
性能指标
- 执行时间
- 吞吐量分析
- 资源利用率
- 延迟细分
-
瓶颈分析
- 已识别瓶颈
- 影响评估
- 优化优先级
-
对比分析(使用--compare参数时)
- 性能趋势
- 提升指标
- 退化检测
-
优化建议
- 优先级行动项
- 预计提升效果
- 实施指南
Usage Examples
使用示例
bash
undefinedbash
undefinedGenerate HTML report with all metrics
生成包含所有指标的HTML报告
npx claude-flow analysis performance-report --format html --include-metrics
npx claude-flow analysis performance-report --format html --include-metrics
Compare current swarm with previous
对比当前集群与历史集群
npx claude-flow analysis performance-report --compare swarm-123 --format markdown
npx claude-flow analysis performance-report --compare swarm-123 --format markdown
Custom output with specific sections
自定义输出指定章节
npx claude-flow analysis performance-report
--sections summary,metrics,recommendations
--output reports$perf-analysis.html
--format html
--sections summary,metrics,recommendations
--output reports$perf-analysis.html
--format html
npx claude-flow analysis performance-report
--sections summary,metrics,recommendations
--output reports/perf-analysis.html
--format html
--sections summary,metrics,recommendations
--output reports/perf-analysis.html
--format html
Weekly performance report
生成每周性能报告
npx claude-flow analysis performance-report
--time-range 7d
--include-metrics
--format markdown
--output docs$weekly-performance.md
--time-range 7d
--include-metrics
--format markdown
--output docs$weekly-performance.md
npx claude-flow analysis performance-report
--time-range 7d
--include-metrics
--format markdown
--output docs/weekly-performance.md
--time-range 7d
--include-metrics
--format markdown
--output docs/weekly-performance.md
JSON format for CI/CD integration
生成JSON格式报告用于CI/CD集成
npx claude-flow analysis performance-report
--format json
--output build$performance.json
--format json
--output build$performance.json
undefinednpx claude-flow analysis performance-report
--format json
--output build/performance.json
--format json
--output build/performance.json
undefinedSample Markdown Report
示例Markdown报告
markdown
undefinedmarkdown
undefinedPerformance Analysis Report
性能分析报告
Executive Summary
执行摘要
- Overall Score: 87/100
- Analysis Period: Last 24 hours
- Swarms Analyzed: 3
- Critical Issues: 1
- 整体得分: 87/100
- 分析周期: 过去24小时
- 分析集群数量: 3
- 关键问题: 1
Key Metrics
关键指标
| Metric | Value | Trend | Target |
|---|---|---|---|
| Avg Task Time | 42s | ↓ 12% | 35s |
| Agent Utilization | 78% | ↑ 5% | 85% |
| Cache Hit Rate | 91% | → | 90% |
| Parallel Efficiency | 2.3x | ↑ 0.4x | 2.5x |
| 指标 | 数值 | 趋势 | 目标 |
|---|---|---|---|
| 平均任务时间 | 42s | ↓ 12% | 35s |
| Agent利用率 | 78% | ↑ 5% | 85% |
| 缓存命中率 | 91% | → | 90% |
| 并行效率 | 2.3x | ↑ 0.4x | 2.5x |
Bottleneck Analysis
瓶颈分析
Critical
严重问题
- Agent Communication Delay (Impact: 35%)
- Coordinator → Coder messages delayed by 2.3s avg
- Fix: Switch to hierarchical topology
- Agent通信延迟(影响占比35%)
- Coordinator → Coder消息平均延迟2.3秒
- 修复方案: 切换至分层拓扑结构
Warnings
警告问题
- Memory Access Pattern (Impact: 18%)
- Neural pattern loading: 1.8s per access
- Fix: Enable memory caching
- 内存访问模式(影响占比18%)
- 神经模式加载每次访问耗时1.8秒
- 修复方案: 启用内存缓存
Recommendations
优化建议
- High Priority: Switch to hierarchical topology (40% improvement)
- Medium Priority: Enable memory caching (25% improvement)
- Low Priority: Increase agent concurrency to 8 (20% improvement)
undefined- 高优先级: 切换至分层拓扑结构(提升40%)
- 中优先级: 启用内存缓存(提升25%)
- 低优先级: 将Agent并发数增加至8(提升20%)
undefined4. Optimization Recommendations
4. 优化建议
Automatic Fixes
自动修复
When using , the following optimizations may be applied:
--fix1. Topology Optimization
- Switch to more efficient topology (mesh → hierarchical)
- Adjust communication patterns
- Reduce coordination overhead
- Optimize message routing
2. Caching Enhancement
- Enable memory caching
- Optimize cache strategies
- Preload common patterns
- Implement cache warming
3. Concurrency Tuning
- Adjust agent counts
- Optimize parallel execution
- Balance workload distribution
- Implement load balancing
4. Priority Adjustment
- Reorder task queues
- Prioritize critical paths
- Reduce wait times
- Implement fair scheduling
5. Resource Optimization
- Optimize memory usage
- Reduce I/O operations
- Batch API calls
- Implement connection pooling
使用参数时,将应用以下优化:
--fix1. 拓扑优化
- 切换至更高效的拓扑结构(网状→分层)
- 调整通信模式
- 减少协调开销
- 优化消息路由
2. 缓存增强
- 启用内存缓存
- 优化缓存策略
- 预加载常用模式
- 实现缓存预热
3. 并发调优
- 调整Agent数量
- 优化并行执行
- 均衡工作负载分配
- 实现负载均衡
4. 优先级调整
- 重新排序任务队列
- 优先处理关键路径
- 减少等待时间
- 实现公平调度
5. 资源优化
- 优化内存使用
- 减少I/O操作
- 批量处理API调用
- 实现连接池
Performance Impact
性能影响
Typical improvements after bottleneck resolution:
- Communication: 30-50% faster message delivery
- Processing: 20-40% reduced task completion time
- Memory: 40-60% fewer cache misses
- Network: 25-45% reduced API latency
- Overall: 25-45% total performance improvement
瓶颈解决后的典型提升效果:
- 通信:消息传递速度提升30-50%
- 处理:任务完成时间减少20-40%
- 内存:缓存未命中次数减少40-60%
- 网络:API延迟降低25-45%
- 整体:总性能提升25-45%
Advanced Usage
高级用法
Continuous Monitoring
持续监控
bash
undefinedbash
undefinedMonitor performance in real-time
实时监控性能
npx claude-flow swarm monitor --interval 5
npx claude-flow swarm monitor --interval 5
Generate hourly reports
生成每小时报告
while true; do
npx claude-flow analysis performance-report
--format json
--output logs$perf-$(date +%Y%m%d-%H%M).json sleep 3600 done
--format json
--output logs$perf-$(date +%Y%m%d-%H%M).json sleep 3600 done
undefinedwhile true; do
npx claude-flow analysis performance-report
--format json
--output logs/perf-$(date +%Y%m%d-%H%M).json sleep 3600 done
--format json
--output logs/perf-$(date +%Y%m%d-%H%M).json sleep 3600 done
undefinedCI/CD Integration
CI/CD集成
yaml
undefinedyaml
undefined.github$workflows$performance.yml
.github/workflows/performance.yml
name: Performance Analysis
on: [push, pull_request]
jobs:
analyze:
runs-on: ubuntu-latest
steps:
- uses: actions$checkout@v2
- name: Run Performance Analysis
run: |
npx claude-flow analysis performance-report
--format json
--output performance.json - name: Check Performance Thresholds run: | npx claude-flow bottleneck detect
--threshold 15
--export bottlenecks.json - name: Upload Reports uses: actions$upload-artifact@v2 with: name: performance-reports path: | performance.json bottlenecks.json
--format json
--output performance.json - name: Check Performance Thresholds run: | npx claude-flow bottleneck detect
--threshold 15
--export bottlenecks.json - name: Upload Reports uses: actions$upload-artifact@v2 with: name: performance-reports path: | performance.json bottlenecks.json
undefinedname: Performance Analysis
on: [push, pull_request]
jobs:
analyze:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: Run Performance Analysis
run: |
npx claude-flow analysis performance-report
--format json
--output performance.json - name: Check Performance Thresholds run: | npx claude-flow bottleneck detect
--threshold 15
--export bottlenecks.json - name: Upload Reports uses: actions/upload-artifact@v2 with: name: performance-reports path: | performance.json bottlenecks.json
--format json
--output performance.json - name: Check Performance Thresholds run: | npx claude-flow bottleneck detect
--threshold 15
--export bottlenecks.json - name: Upload Reports uses: actions/upload-artifact@v2 with: name: performance-reports path: | performance.json bottlenecks.json
undefinedCustom Analysis Scripts
自定义分析脚本
javascript
// scripts$analyze-performance.js
const { exec } = require('child_process');
const fs = require('fs');
async function analyzePerformance() {
// Run bottleneck detection
const bottlenecks = await runCommand(
'npx claude-flow bottleneck detect --format json'
);
// Generate performance report
const report = await runCommand(
'npx claude-flow analysis performance-report --format json'
);
// Analyze results
const analysis = {
bottlenecks: JSON.parse(bottlenecks),
performance: JSON.parse(report),
timestamp: new Date().toISOString()
};
// Save combined analysis
fs.writeFileSync(
'analysis$combined-report.json',
JSON.stringify(analysis, null, 2)
);
// Generate alerts if needed
if (analysis.bottlenecks.critical.length > 0) {
console.error('CRITICAL: Performance bottlenecks detected!');
process.exit(1);
}
}
function runCommand(cmd) {
return new Promise((resolve, reject) => {
exec(cmd, (error, stdout, stderr) => {
if (error) reject(error);
else resolve(stdout);
});
});
}
analyzePerformance().catch(console.error);javascript
// scripts/analyze-performance.js
const { exec } = require('child_process');
const fs = require('fs');
async function analyzePerformance() {
// 运行瓶颈检测
const bottlenecks = await runCommand(
'npx claude-flow bottleneck detect --format json'
);
// 生成性能报告
const report = await runCommand(
'npx claude-flow analysis performance-report --format json'
);
// 分析结果
const analysis = {
bottlenecks: JSON.parse(bottlenecks),
performance: JSON.parse(report),
timestamp: new Date().toISOString()
};
// 保存合并分析结果
fs.writeFileSync(
'analysis/combined-report.json',
JSON.stringify(analysis, null, 2)
);
// 必要时生成告警
if (analysis.bottlenecks.critical.length > 0) {
console.error('CRITICAL: 检测到性能瓶颈!');
process.exit(1);
}
}
function runCommand(cmd) {
return new Promise((resolve, reject) => {
exec(cmd, (error, stdout, stderr) => {
if (error) reject(error);
else resolve(stdout);
});
});
}
analyzePerformance().catch(console.error);Best Practices
最佳实践
1. Regular Analysis
1. 定期分析
- Run bottleneck detection after major changes
- Generate weekly performance reports
- Monitor trends over time
- Set up automated alerts
- 重大变更后运行瓶颈检测
- 生成每周性能报告
- 长期监控趋势
- 设置自动告警
2. Threshold Tuning
2. 阈值调优
- Start with default threshold (20%)
- Lower for production systems (10-15%)
- Higher for development (25-30%)
- Adjust based on requirements
- 从默认阈值(20%)开始
- 生产环境降低阈值(10-15%)
- 开发环境提高阈值(25-30%)
- 根据需求调整
3. Fix Strategy
3. 修复策略
- Always review before applying --fix
- Test fixes in development first
- Apply fixes incrementally
- Monitor impact after changes
- 应用--fix前务必审核
- 先在开发环境测试修复
- 逐步应用修复
- 修复后监控影响
4. Report Integration
4. 报告集成
- Include in documentation
- Share with team regularly
- Track improvements over time
- Use for capacity planning
- 纳入文档
- 定期与团队共享
- 跟踪长期提升效果
- 用于容量规划
5. Continuous Optimization
5. 持续优化
- Learn from each analysis
- Build performance budgets
- Establish baselines
- Set improvement goals
- 从每次分析中学习
- 建立性能预算
- 设立基准线
- 制定提升目标
Troubleshooting
故障排查
Common Issues
常见问题
High Memory Usage
bash
undefined高内存占用
bash
undefinedAnalyze memory bottlenecks
分析内存瓶颈
npx claude-flow bottleneck detect --threshold 10
npx claude-flow bottleneck detect --threshold 10
Check cache performance
检查缓存性能
npx claude-flow cache manage --action stats
npx claude-flow cache manage --action stats
Review memory metrics
查看内存指标
npx claude-flow memory usage
**Slow Task Execution**
```bashnpx claude-flow memory usage
**任务执行缓慢**
```bashIdentify slow tasks
识别缓慢任务
npx claude-flow task status --detailed
npx claude-flow task status --detailed
Analyze coordination overhead
分析协调开销
npx claude-flow bottleneck detect --time-range 1h
npx claude-flow bottleneck detect --time-range 1h
Check agent utilization
检查Agent利用率
npx claude-flow agent metrics
**Poor Cache Performance**
```bashnpx claude-flow agent metrics
**缓存性能不佳**
```bashAnalyze cache hit rates
分析缓存命中率
npx claude-flow analysis performance-report --sections metrics
npx claude-flow analysis performance-report --sections metrics
Review cache strategy
审核缓存策略
npx claude-flow cache manage --action analyze
npx claude-flow cache manage --action analyze
Enable cache warming
启用缓存预热
npx claude-flow bottleneck detect --fix
undefinednpx claude-flow bottleneck detect --fix
undefinedIntegration with Other Skills
与其他Skill集成
- swarm-orchestration: Use performance data to optimize topology
- memory-management: Improve cache strategies based on analysis
- task-coordination: Adjust scheduling based on bottlenecks
- neural-training: Train patterns from performance data
- swarm-orchestration:利用性能数据优化拓扑结构
- memory-management:基于分析结果改进缓存策略
- task-coordination:根据瓶颈调整调度
- neural-training:从性能数据中训练模式
Related Commands
相关命令
- - Real-time monitoring
npx claude-flow swarm monitor - - Token optimization analysis
npx claude-flow token usage - - Cache optimization
npx claude-flow cache manage - - Agent performance metrics
npx claude-flow agent metrics - - Task execution analysis
npx claude-flow task status
- - 实时监控
npx claude-flow swarm monitor - - Token优化分析
npx claude-flow token usage - - 缓存优化
npx claude-flow cache manage - - Agent性能指标
npx claude-flow agent metrics - - 任务执行分析
npx claude-flow task status
See Also
另请参阅
- Bottleneck Detection Guide
- Performance Report Guide
- Performance Bottlenecks Overview
- Swarm Monitoring Documentation
- Memory Management Documentation
Version: 1.0.0
Last Updated: 2025-10-19
Maintainer: Claude Flow Team
- 瓶颈检测指南
- 性能报告指南
- 性能瓶颈概述
- 集群监控文档
- 内存管理文档
版本: 1.0.0
最后更新: 2025-10-19
维护者: Claude Flow团队