Skip to main content
Standard Mode and Boost Mode are cloud extraction options for running Octoparse tasks. They are designed for different performance needs. Use Standard Mode for regular cloud extraction. Use Boost Mode when the task and plan support higher-speed or higher-concurrency execution.

​
How it works

​
Standard Mode

In Standard Mode, the entire task runs on a single cloud node without being divided. All data records are collected sequentially by that one node. This keeps the workflow simple and predictable, but means that if the run is interrupted — due to a website error, or a timeout — the task has to restart from the beginning. For large datasets, a single long-running node also increases the risk of mid-run failures. Standard Mode is best suited for small datasets, test runs, or websites that only allow one active login session at a time.

​
Boost Mode

In Boost Mode, the task is automatically split into multiple sub-tasks. Each sub-task is assigned to one cloud node and collects only a portion of the total data. The number of sub-tasks depends on the specific task configuration. This parallel approach offers several advantages:
  • Faster completion — Sub-tasks run concurrently, reducing overall run time significantly.
  • Lower risk of data loss — Each sub-task only handles a smaller portion of data, so a mid-run failure affects fewer records.
  • Independent recovery — If one sub-task fails, it can be restarted individually without affecting or re-running the others, saving significant recovery time.
Boost Mode is recommended for large-scale data collection where speed and resilience are priorities.

​
Comparison

AreaStandard ModeBoost Mode
How it worksOne task runs on a single cloud node, no sub-tasksTask is split into multiple sub-tasks, each run by a separate cloud node
Best forSmall datasets, testing, or single-session websitesLarge-scale extraction where speed and resilience matter
PerformanceNormal cloud executionHigher-speed parallel execution
Failure impactA failure interrupts the entire taskOnly the affected sub-task is interrupted; others continue unaffected
RecoveryMust restart the full taskRestart only the failed sub-task
Cost/availabilityDepends on planMay require specific plan or usage allowance
Recommended useFor stable, smaller tasksUse when speed matters and the task supports concurrent execution

​
When to use Standard Mode

Use Standard Mode when:
  • You are running a normal scheduled task
  • Speed is not the main constraint
  • You want a stable default cloud run mode
  • The dataset size is moderate
  • You are still validating task reliability
  • The target website only allows one active session at a time
Standard Mode is usually the starting point for cloud extraction.

​
When to use Boost Mode

Use Boost Mode when:
  • You need faster extraction
  • The task collects a larger dataset
  • The task can safely run with higher concurrency
  • You have already tested the workflow
  • Your plan supports the mode
Boost Mode is most useful when the bottleneck is run time and the task can handle faster execution without triggering site issues.

​
What to check before using Boost Mode

Before switching a task to Boost Mode, check:
  • The target website can handle faster requests or higher activity
  • Pagination and detail page workflows remain stable
  • Anti-bot or rate-limit issues do not increase
  • Output quality remains consistent
  • Your plan supports the required cloud resources
Faster extraction is not always better. Some websites are more likely to fail, block requests, or return incomplete data when a task runs too aggressively.
1

Run locally first

Confirm the task captures the correct fields and page flow.
2

Run in Standard Mode

Validate that the task works in the cloud environment.
3

Try Boost Mode when needed

Use Boost Mode only after the task is stable and speed is a real requirement.
4

Compare output

Check record count, missing fields, duplicates, and errors after switching modes.