Skip to content

Performance Optimization

Tune OS, client settings, and profile count for faster launches and stable multi-profile runs.

1. Metrics

  • Startup — profile ready in < ~5 s (hardware dependent)
  • Memory — aim for manageable per-profile footprint
  • CPU — avoid sustained >70% on typical desktops
  • Concurrency — how many profiles run together without swap thrashing

2. System tuning (Windows)

  • Power plan: High performance
  • 16 GB+ RAM recommended for 5+ concurrent profiles
  • SSD for profile + cache directories
  • Close unused background apps
  • Optional: trim SysMain/Superfetch only if you understand the tradeoff

Virtual memory

Set page file on SSD (~1.5× RAM) if you often run many profiles.

3. Client / Chromium flags (examples)

json
{
  "browser": {
    "args": [
      "--disable-background-timer-throttling",
      "--disable-renderer-backgrounding",
      "--memory-pressure-off"
    ]
  },
  "memory": {
    "maxMemory": 2048,
    "gcInterval": 30000,
    "autoCleanup": true
  }
}

Adjust maxMemory per machine; lower when running 10+ profiles.

4. Concurrency

json
{
  "concurrency": {
    "maxInstances": 10,
    "instanceStartupDelay": 1000,
    "enableStaggeredStartup": true
  }
}

Stagger launches to avoid I/O spikes. On 8 GB RAM, start with 3–5 profiles max.

5. Network

  • Reuse healthy proxies; drop dead nodes quickly
  • Reasonable connection limits per host
  • DNS cache / reliable resolvers (8.8.8.8, 1.1.1.1)

6. Cache

json
{
  "cache": {
    "enableDiskCache": true,
    "diskCacheSize": 100,
    "cleanupInterval": 86400000
  }
}

Schedule cache cleanup weekly on automation workloads.

7. Monitoring

Watch Task Manager / Activity Monitor:

  • Virtual Browser total RAM
  • Disk queue length
  • Failed proxy ratio

If memory climbs over hours, restart the client or reduce open profiles.

8. Practices

DoAvoid
Batch create/start via API/CLIStarting 20 profiles at once on 8 GB RAM
Clear cache after crawlsHuge extensions on every profile
Match kernel to target sitesIdentical heavy tabs in all profiles

9. Testing

  • Baseline: one profile, cold start
  • Load: N profiles with typical sites
  • Compare before/after flag changes

See also Troubleshooting and System requirements.