1. Commerce
  2. NetSuite Point of Sale (NSPOS)
  3. NSPOS Administrator Guide
  4. Environment – Required
  5. Benchmarks for Data Transfers and System Limits

Benchmarks for Data Transfers and System Limits

The benchmark statistics presented in this topic are from tests run on a NetSuite Point of Sale (NSPOS) 2020.1.x environment.

The numbers represent the benchmark data-transfer rates for synchronizing information between NSPOS register terminals and NetSuite ERP. The topic includes scenarios for improving data throughput and provides system limitations for activities such as staging new registers. Transfers occur through a cloud-based replication server typical to the servers assigned to customers.

Upsync Transfers from NetSuite POS to NetSuite ERP

These transfers from the POS use two steps:

Sending data from POS Terminals to the Replication Server

There should be almost no delay in getting data from POS terminals to the replication server. Transfers happen in near real-time. You can expect delays if a register is processing transactions offline (without replication server connectivity) and at some point is reconnected.

Processing backlogged data from a Terminal to the Replication Server

If a register is processing transactions offline (without replication server connectivity) and at some point is reconnected, the delay in sending data from a terminal to the replication server depends on how many transactions there are.

For example, if a customer has 100 terminals processing transactions that went offline for 3 days, and there are 10,000 transactions a day from all terminals distributed equally, then the statistics for catching up and becoming current on the replication server are:

Important:

These numbers are for a normal workload. If you perform a mass update in NetSuite ERP, it can significantly slow down the transfer of data from the POS terminals to the replication server. This is because replication server to terminal transfers have a higher priority than terminal to replication server transfers.

Sending data from the Replication Server to NetSuite ERP

The replication server sends data to NetSuite ERP via NetSuite SOAP Web Services. Bandwidth depends on number of available connections and the average item count per transaction. The following chart lists the average bandwidth defined as the number of transactions per hour.

Number of connections

Average item count per transaction

3

5 (default)

10

20

50

1

650

700

640

510

300

5 (default)

3200

3500

3200

2500

1400

10

6600

6900

6000

4500

2200

20

10800

10000

7200

5200

2400
Note:

The default connection setup is 5 x 5. This default can be adjusted based on customer needs.

20 dedicated connections to NetSuite ERP will usually provide the best performance, but some customers will have different requirements. Free slots must be available for downsync and real-time services such as sales orders and returns. If needed, contact NetSuite Customer Support for assistance to create the optimal configuration.

Downsync Transfers from NetSuite ERP to NetSuite POS

These transfers also use two steps:

The current average bandwidth per hour is:

Location / Terminal Influence on Downsync

Downsync bandwidth is strongly influenced by how many locations or terminals you have. The downsync numbers listed here are valid for up to 100 locations or 200 terminals. The more locations, the smaller the bandwidth. The dependency is not linear.

Replicating Partner Limit

We support up to 1,200 replicating partners on one standard implementation. Replicating partners are Standalone terminals and Server with POS terminals provide database services to other registers.

On-demand, single register staging

On-demand staging is initiated from a register’s RA-Workstation record. The process uses an installation URL to download a staging package to the register represented by the record.

Limitations:

Related Topics

General Notices