ClashXノード速度テストと選択のヒント：最速プロキシサーバーを見つける

遅延指標の理解

速度テストは主に以下の指標に焦点を当てます：

遅延（レイテンシー / Ping）

データがデバイスからプロキシサーバーに到達して戻るまでに必要な時間で、ミリ秒（ms）で測定されます。

パケットロス

宛先に到達できなかったデータパケットの割合です。1%以上のパケットロスはユーザー体験に影響し、特にリアルタイムアプリケーション（ゲーム、ビデオ通話）で顕著です。

帯域幅

ノードが提供できる最大データ転送速度です。注意：ClashXの遅延テストでは帯域幅は測定されません。実際の使用または専用の速度テストツールで評価する必要があります。

手動テスト方法

方法1：ClashX内蔵速度テスト

最もシンプルで直接的な速度テスト方法：

1. メニューバーのClashXアイコンをクリック
2. 「プロキシ」メニューを選択
3. 「遅延テスト」（ベンチマーク）をクリック
4. 数秒待つと、すべてのノードの横に遅延値が表示されます

Method 2: Policy Group Speed Test

If you use policy groups (such as url-test), you can test a specific policy group separately:

1. メニューバーのClashXアイコンをクリック
2. Select the corresponding policy group
3. Right-click the policy group name
4. Select "Test latency"

Method 3: Dashboard Speed Test

Use the web control panel for more detailed speed testing:

1. Visit http://127.0.0.1:9090/ui
2. Click the "Proxies" tab
3. Select the policy group or node to test
4. Click the speed test button (lightning icon)

The advantage of Dashboard is viewing more detailed information, including speed test history.

自動テスト設定

手動速度テストはシンプルですが頻繁な操作が必要です。より良い方法は、自動速度テストポリシーグループを設定することです。

url-test 自動選択

遅延が最も低いノードを自動的に選択します：

proxy-groups:
  - name: "♻️ Auto Select"
    type: url-test
    proxies:
      - "Hong Kong 01"
      - "Hong Kong 02"
      - "Japan 01"
      - "US 01"
    url: "http://www.gstatic.com/generate_204"
    interval: 300      # Test every 300 seconds
    tolerance: 50      # Do not switch when the latency gap is under 50 ms

Key Parameter Description

• url: Speed test target URL. Recommended to use http://www.gstatic.com/generate_204, a lightweight and fast speed test address
• interval: Testing interval (seconds). Recommended 300-600 seconds, too frequent wastes resources
• tolerance: Tolerance value (milliseconds). New node must be faster than current node by more than this value to switch, avoiding frequent jumping

fallback Failover

Automatically switches when the main node fails:

proxy-groups:
  - name: "🔰 Failover"
    type: fallback
    proxies:
      - "primary node"
      - "backup node 1"
      - "backup node 2"
    url: "http://www.gstatic.com/generate_204"
    interval: 300
    timeout: 2000  # Timeout: 2000 ms

load-balance Load Balancing

Distributes traffic among multiple healthy nodes:

proxy-groups:
  - name: "⚖️ Load Balancing"
    type: load-balance
    proxies:
      - "Node 1"
      - "Node 2"
      - "Node 3"
    url: "http://www.gstatic.com/generate_204"
    interval: 300
    strategy: consistent-hashing  # Or use round-robin

strategy parameter:

• consistent-hashing: Allocates based on destination address, same website always uses same node, suitable for session-preserving scenarios
• round-robin: Round-robin allocation, each request uses different node, suitable for downloading scenarios

ノード選択戦略

目的別に選択

異なる使用シーンには異なるタイプのノードが必要です：

Select by Geographic Location

Geographic location has a significant impact on latency:

• China Mainland Users: Hong Kong, Taiwan, Japan, Singapore nodes typically have lowest latency (20-80ms)
• European Users: Local European nodes are best
• Cross-border Access: When accessing services in specific countries, selecting nodes in that country usually works best

Route Quality Identification

Common route types (descending quality):

1. IPLC / IEPL Dedicated Line: Point-to-point dedicated line, low latency, high stability, expensive
2. CN2 GIA: Premium telecom route, low latency, stable during peak hours
3. CN2 GT: Standard telecom route, good value
4. BGP Multi-line: Automatically selects carrier routing
5. Regular Route: Cheap but may be congested during peak hours

パフォーマンス最適化のヒント

1. Multiple Node Backup

Configure fallback policy group to ensure automatic switching when main node fails:

proxy-groups:
  - name: "🚀 Primary Nodes"
    type: fallback
    proxies:
      - "Hong Kong IPLC 01"
      - "Hong Kong CN2 01"
      - "Japan 01"
    url: "http://www.gstatic.com/generate_204"
    interval: 300

2. Traffic Splitting Strategy

Configure different node groups for different services:

proxy-groups:
  - name: "🎬 Streaming"
    type: select
    proxies:
      - "US Node Group"
      - "Hong Kong Node Group"

  - name: "🎮 Gaming"
    type: url-test
    proxies:
      - "Low-Latency Node 1"
      - "Low-Latency Node 2"
    interval: 60  # Game traffic can be tested more frequently

  - name: "📥 Downloads"
    type: load-balance
    proxies:
      - "High-Bandwidth Node 1"
      - "High-Bandwidth Node 2"

3. Speed Test URL Selection

Different speed test URLs may give different results:

• http://www.gstatic.com/generate_204 - Google service, globally applicable
• https://cp.cloudflare.com/generate_204 - Cloudflare, suitable for CDN testing
• http://www.apple.com/library/test/success.html - Apple, suitable for iOS users

4. Regular Maintenance

Develop good maintenance habits:

• Manually test speed once a week to understand node status
• Delete long-term failed nodes promptly
• Follow service provider notifications for maintenance and upgrade information
• Testing during peak hours (8-11 PM) better reflects actual conditions

5. Use Dashboard Monitoring

Web Dashboard provides real-time monitoring and history:

• View currently used nodes
• View traffic and latency for each connection
• Analyze which apps use the most traffic
• Discover abnormal traffic and connections