ClashX Node Speed Testing and Selection Tips: Find the Fastest Proxy Сервер

Article 11 cover image

Why Speed Testing

Choosing the right прокси-узел is crucial for сеть experience. Different nodes have varying latency, bandwidth, and stability, which directly affect:

  • Page Load Speed: Low-latency nodes load web pages faster
  • Video Streaming: High-bandwidth nodes are suitable for HD video
  • Gaming Experience: Стабильный low-latency nodes reduce lag
  • Download Speed: Quality routes fully utilize your bandwidth
💡
Лучшие практики

Regular тест скоростиing рекомендуется as node производительность changes with time and сеть conditions. ClashX can be configured for automatic тест скоростиing to ensure you always use the optimal node.

Understanding latency Metrics

Speed testing mainly focuses on the following metrics:

latency (latency / Ping)

The time required for data to travel from your device to the прокси-сервер and back, measured in milliseconds (ms).

< 50ms
Отлично
50-100ms
Хорошо
100-200ms
Удовлетворительно
200-500ms
Плохо
> 500ms
Очень плохо

Потеря пакетов

The percentage of data packets that fail to reach their destination. Packet loss above 1% affects user experience, especially for в реальном времени applications (gaming, video calls).

Пропускная способность

The maximum data transfer rate a node can provide. Note: ClashX's тест задержки doesn't measure bandwidth; it needs to be evaluated through actual use or dedicated тест скорости tools.

⚠️
Limitations of Speed Testing

Speed test results are only for reference. Actual experience is also affected by сервер load, routing оптимизация, target website location, and other factors.

Manual Testing Methods

Method 1: ClashX Built-in Speed Test

The simplest and most direct тест скоростиing method:

  1. Click the ClashX icon in the строка меню
  2. Select "Proxy" menu
  3. Click "latency Test" (Benchmark)
  4. Wait a few seconds, latency values will appear next to all nodes

Speed Test Shortcut

You can set a shortcut for тест задержкиing:

1. Open "System Preferences" → "Keyboard" → "Shortcuts" → "App Shortcuts"
2. Add ClashX, enter menu title "Benchmark"
3. Set your preferred shortcut, such as ⌘⇧T

Method 2: Policy Group Speed Test

If you use группа политикs (such as url-test), вы можете test a specific группа политик separately:

  1. Click the ClashX icon in the строка меню
  2. Select the corresponding группа политик
  3. Right-click the группа политик name
  4. Select "Test latency"

Method 3: Dashboard Speed Test

Use the web control panel for more detailed тест скоростиing:

  1. Visit http://127.0.0.1:9090/ui
  2. Click the "Proxies" tab
  3. Select the группа политик or node to test
  4. Click the тест скорости button (lightning icon)

The advantage of Dashboard is viewing more detailed information, including тест скорости history.

Automatic Testing Configuration

Manual тест скоростиing is simple but requires frequent operation. A better approach is to configure automatic тест скорости группа политикs.

url-test Auto-Select

Automatically selects the node with the lowest latency:

proxy-groups:
  - name: "♻️ 自动选择"
    type: url-test
    proxies:
      - "香港 01"
      - "香港 02"
      - "日本 01"
      - "美国 01"
    url: "http://www.gstatic.com/generate_204"
    interval: 300      # 每 300 秒测试一次
    tolerance: 50      # 延迟差异小于 50ms 不切换

Key Parameter Description

  • url: Speed test target URL. Recommended to use http://www.gstatic.com/generate_204, a lightweight and fast тест скорости 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: "🔰 故障转移"
    type: fallback
    proxies:
      - "主节点"
      - "备用节点 1"
      - "备用节点 2"
    url: "http://www.gstatic.com/generate_204"
    interval: 300
    timeout: 2000  # 超时时间 2000ms

load-balance Балансировка нагрузки

Distributes трафик among multiple healthy nodes:

proxy-groups:
  - name: "⚖️ 负载均衡"
    type: load-balance
    proxies:
      - "节点 1"
      - "节点 2"
      - "节点 3"
    url: "http://www.gstatic.com/generate_204"
    interval: 300
    strategy: consistent-hashing  # 或 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
💡
Combining Policy Groups

You can create a url-test auto-select group, then include it in a select manual selection group. This provides both automatic оптимизация and manual control flexibility.

Node Selection Strategies

Select by Purpose

Different usage scenarios require different types of nodes:

Usage Scenario Recommended Features Node Type
Web Browsing Low latency Nearby nodes (Hong Kong, Japan, Singapore)
Video Streaming High Bandwidth, Стабильный Content location node (e.g., US node for Netflix US content)
Gaming Acceleration Ultra-low latency, Low Packet Loss Quality routes to game сервер location
Large File Downloads High Bandwidth Load balancing group or high-speed dedicated line
Daily Work Stability fallback failover group

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
⚠️
Pitfalls to Avoid

• Don't just look at latency, also pay attention to stability and actual speed
• Daytime test results may differ from evening peak hours
• Don't put all трафик on one node

Производительность Оптимизация Tips

1. Multiple Node Backup

Configure fallback группа политик to ensure automatic switching when main node fails:

proxy-groups:
  - name: "🚀 主力节点"
    type: fallback
    proxies:
      - "香港 IPLC 01"
      - "香港 CN2 01"
      - "日本 01"
    url: "http://www.gstatic.com/generate_204"
    interval: 300

2. Трафик Splitting Strategy

Configure different node groups for different services:

proxy-groups:
  - name: "🎬 流媒体"
    type: select
    proxies:
      - "美国节点组"
      - "香港节点组"

  - name: "🎮 游戏"
    type: url-test
    proxies:
      - "低延迟节点 1"
      - "低延迟节点 2"
    interval: 60  # 游戏场景可以更频繁测速

  - name: "📥 下载"
    type: load-balance
    proxies:
      - "高带宽节点 1"
      - "高带宽节点 2"

3. Speed Test URL Selection

Different тест скорости 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 Мониторинг

Web Dashboard provides в реальном времени monitoring and history:

  • View currently used nodes
  • View трафик and latency for each connection
  • Analyze which apps use the most трафик
  • Discover abnormal трафик and connections

Node Selection Summary

Лучшие практики:

  • Use url-test to auto-select nodes for daily browsing
  • Use fallback to ensure critical service stability
  • Configure dedicated группа политикs for special purposes (streaming, gaming)
  • Regularly manually test speed to understand true node conditions
  • Don't over-rely on automatic тест скоростиing, adjust based on actual experience