Understanding the ERP.net's Network Test: when, how, and what it tells you

Reliable network performance is crucial for the smooth operation of your ERP system.

ERP.net provides a built-in Network Test tool to help diagnose potential issues related to latency, throughput, or data load times. This blog post outlines when to run the test, how to do it, and how to interpret the results, using real data and clear benchmarks.

When should you run the Network Test?

Run the ERP.net Network Test when you're facing one or more of the following recurring issues:

• Slow loading of forms or documents

• Delays during save operations or state transitions

• Noticeable latency when opening navigators or reports

• Overall sluggishness, where users describe the experience as “everything feels slow”

These symptoms often indicate underlying issues with network speed, latency, or data throughput. Running the test helps determine whether the cause is network-related, enabling faster diagnosis and resolution. 

💡 Tip: The Network Test becomes especially valuable when used alongside the Remoting Log. The Remoting Log shows performance breakdowns for server operations, including detailed timing for:

• Client execution time

• Network time

• Server processing time

If you notice that a significant portion of the total time is consumed by “Network, ms”, this may indicate a network bottleneck rather than a server-side issue. Running the Network Test in such cases can confirm whether poor throughput or high latency is the root cause.

How to launch the Network Test in ERP.net

Follow these steps to perform a network diagnostic test:

1. Open the ERP.net Desktop Client

2. Go to the File tab

3. Click on Settings

4. Select the Network Test button

This will open a new Network Test window.

     5. Click the Start Test button

This will start a diagnostic test and output a detailed log of several typical ERP operations and their performance over your current network.

    6. Once the test completes:

• Use the Copy Log button to copy the full output to your clipboard for review or sharing through the desired channel.

• Alternatively, click Send as Mail to automatically open a new email where you can paste the log and send it for review - ideal for reporting to support or your system administrator.

This diagnostic log is the key to identifying whether any performance issues are related to your network, application load, or server responsiveness.

Example output and how to read it

Here’s a sample of what the test output might look like:

[2025.06.11 02:17:17.] Start. Use HTTP GZip: True 
[2025.06.11 02:17:29.] 1,500 * GetDateTimeNowUtc: 4,003 ms; Avg: 2 ms;
[2025.06.11 02:17:33.] 1,000 * Load 3 rows: 3,886 ms; Avg: 3 ms;
[2025.06.11 02:17:39.] 10 * Load 10,000 rows: 5,625 ms; Avg: 562 ms;
[2025.06.11 02:17:39.] Finish
[2025.06.11 02:17:39.] Total time: 13,514 ms; Network 21.76 MB; Application: 116.41 MB;
[2025.06.11 02:17:39.] Throughput: 8.61 MB/s; Latency: 2 ms;

What this shows:

• HTTP GZip: True
  Compression is enabled to reduce the size of data transferred over the network.

• 1,500 calls to GetDateTimeNowUtc
  Executed in 4,003 ms total, with an average of 2 ms per call—this is a fast response time for a lightweight operation.

• 1,000 requests loading 3 rows each
  Completed in 3,886 ms, averaging 3 ms per request—indicates strong performance for small data operations.

• 10 requests loading 10,000 rows
  Took 5,625 ms total, with an average of 562 ms per request—this is within the normal range for bulk data loads and reflects the expected impact of payload size.

• Total time: 13,514 ms
  Represents the full test duration across all operations.

• Network: 21.76 MB; Application: 116.41 MB
  Shows compressed data transfer size (network) versus actual processed data (application), indicating effective GZip compression.

• Throughput: 8.61 MB/s

  Throughput refers to the amount of data that can be transferred per second over the network. At 8.61 megabytes per second, this is a good value for business applications.

• Latency: 2 ms

  Latency is the round-trip delay between sending a request and receiving a response. A value of 2 milliseconds is considered local-grade latency and indicates a very fast and responsive connection.

This data enables you to pinpoint potential performance issues—whether in network transmission, database access, or server-side computation. Refer to the thresholds in the next section to interpret these values in context.

General thresholds for ERP application performance

Here is a reference table to help interpret the results:

Use this chart to evaluate your results. If your test falls into the "Warning" column, it may indicate issues that should be discussed with your IT provider or infrastructure team.

Final thoughts

The Network Test is a simple yet powerful tool for identifying performance bottlenecks and understanding the behavior of your ERP system under various loads. By running this test and reviewing the results using the guide above, consultants and end users can quickly pinpoint whether issues stem from network limitations or other root causes.

If you’d like help interpreting results or optimizing your ERP setup based on test findings, feel free to contact your support consultant or our technical team.