# NetSuite Integration Throughput Calculator

> Source: https://netray.co/tools/netsuite-integration-throughput-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Estimate how many records per hour an integration can load and how long a migration will take, from call time, concurrency and retries.

## Category

netsuite

## Erp

NetSuite

## Audience

- Integration developer
- NetSuite architect
- Data migration lead

## Tool

**Kind:** calculator

**Inputs:**

#### Records to load

**Key:** records

**Type:** number

**Default:** 250000

**Min:** 1

**Step:** 1000

**Unit:** records

**Help:** Total records, including line items counted as separate calls if you send them separately.

#### Records per call

**Key:** per_call

**Type:** number

**Default:** 1

**Min:** 1

**Step:** 1

**Unit:** records

**Help:** Use 1 for record-by-record APIs, or the batch size if your call handles several.

#### Average call time

**Key:** call_sec

**Type:** number

**Default:** 1.8

**Min:** 0.1

**Step:** 0.1

**Unit:** seconds

**Help:** Measure in sandbox with realistic payloads and scripts.

#### Parallel threads used

**Key:** concurrency

**Type:** slider

**Default:** 4

**Min:** 1

**Max:** 20

**Step:** 1

**Help:** Do not exceed your account's concurrency allowance.

#### Retry or failure rate

**Key:** retry

**Type:** number

**Default:** 3

**Min:** 0

**Max:** 50

**Step:** 0.5

**Unit:** %

**Help:** Share of calls repeated because of errors or timeouts.

#### Daily load window

**Key:** window

**Type:** number

**Default:** 8

**Min:** 1

**Max:** 24

**Step:** 1

**Unit:** hours

**Outputs:**

#### Effective seconds per call

**Key:** effective_sec

**Expr:** call_sec * (1 + retry / 100)

**Format:** decimal

#### Total calls

**Key:** calls

**Expr:** ceil(records / per_call)

**Format:** integer

#### Records per hour

**Key:** rate

**Expr:** concurrency * 3600 / effective_sec * per_call

**Format:** integer

**Description:** Throughput across all threads.

#### Total load time

**Key:** hours

**Expr:** records / rate

**Format:** hours

**Primary:** true

**Description:** Elapsed hours if the load runs continuously.

#### Working days in window

**Key:** days

**Expr:** ceil(hours / window)

**Format:** integer

**Primary:** true

**Description:** Days needed if loading only within the daily window.

**Chart:**

#### Load time (hours) vs parallel threads

**Type:** line

**X:** concurrency

**From:** 1

**To:** 20

**Steps:** 20

**Series:**

- hours

**Disclaimer:** A planning estimate only. Real throughput depends on scripts and workflows on the record, account concurrency limits, record complexity and time of day. Measure with a representative sample in sandbox first.

## Content

**Intro:** Before you promise a migration date, estimate how long the load will take. This calculator turns average call time, parallel threads and retry rate into records per hour and total load time, and shows how adding threads changes the answer.

**Sections:**

#### How to use the calculator

**Body:** Enter the number of records and how many go in each call. Measure the average call time in a sandbox with realistic data, since customizations on the record change it a lot. Set the number of parallel threads you plan to use and the share of calls you expect to retry. The result gives records per hour, total hours, and the number of days if you only load in a set window each day. The chart sweeps threads from 1 to 20.

**Bullets:**

- Measure call time with real payloads
- Count child lines as calls if they are sent separately
- Keep threads within your concurrency allowance
- Re-measure when scripts or workflows change

#### The formula

**Body:** Effective call time is the average call time times one plus the retry rate. Records per hour is threads times 3600, divided by the effective call time, times records per call. Total time is records divided by that rate. The model assumes calls are independent and that threads do not slow each other. In practice, more threads can raise the average call time through lock contention and governance limits, so treat the high-thread end of the chart as an upper bound.

#### Reading the result and common mistakes

**Body:** Use the result to compare loading strategies: more threads, larger batches, disabling nonessential scripts for the load where policy allows, or splitting the load across several nights. The usual mistakes are measuring on an empty sandbox, ignoring that user event scripts and workflows fire on each record, and forgetting that business users share the same account concurrency during the day.

**Bullets:**

- Test in a sandbox with production-like scripts
- Plan for a re-run of failed records
- Avoid loading during peak business hours
- Check concurrency limits for your account and service tier

**Cta:** If you need to load or sync large volumes from another system, Netray can help design and build the integration and validate it against your account.

**Faq:**

#### Why is my real throughput lower than the estimate?

**Answer:** Parallel calls to the same account can queue, scripts and workflows add time per record, and locks on shared records such as items or customers can serialize updates. Measure with the real thread count rather than extrapolating from one.

#### What is a good retry rate?

**Answer:** Start with a few percent for planning and measure in sandbox. A high retry rate usually points to a validation problem or lock contention that should be fixed rather than tolerated.

#### Does batching help?

**Answer:** It can, when the interface supports several records per call, because it cuts the per-call overhead. Compare the time per record, not the time per call, and check limits on payload size.

#### Is this specific to one NetSuite API?

**Answer:** No. It is a generic model that works for REST, SOAP web services, RESTlets or CSV import jobs, as long as you supply a measured call time and a concurrency you are allowed to use.

## Search terms

netsuite integration throughput, netsuite data load time estimate, netsuite api concurrency calculator, netsuite migration duration, netsuite records per hour, netsuite bulk load planning

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json