Execu/Tech Systems, Inc.
Knowledgebase
Search:
850-747-0581 Email Website
Contents
 
:
IndexBookmarkPrint This Article

Home > Errors / Fixes > Network Benchmark

Execu/Suite Network Health Benchmark (ETBenchmark)

Execu/Tech Systems is not responsible for your network and computer hardware. If you're experiencing network or computer hardware related problems, we provide this benchmark tool for your network technician, but we can't fix these problems for you.

This is an unsupported FREE utility. Our technicians can't help you with it and the only information available for this utility is on this page.

 

If you're receiving a poor benchmark score, make sure that your antivirus is properly configured. Recommended firewall configuration can be found here: System Requirements

 

 Look at the bottom of this page for information on how to read the benchmark results.

 

Because it's often difficult for technicians to determine whether or not your network is adequate to run our software, we provide a benchmark application that provides a score and lets you know what you can expect.

  • Copying files across the network is not an accurate test for database access. This benchmark will gauge your network infrastructure's ability to perform well with our software. 
  • This benchmark application is testing file IO per second, not copying a single large file. File IO can be affected by many pieces of your network, server and client hardware, other applications including antivirus, etc.
  • This benchmark application only tests the time it takes to open a file, read it, write one record and then save the file across the network. This isn't necessarily an indication of your overall network speed, internet speed or speed when transferring large files.
  • This benchmark application won't detect intermittent network problems if they don't happen while the test is running. Any sudden jumps in the score, up or down, could be a sign of an intermittent network problem.
  • This benchmark should only be used to gauge potential performance when using Execu/Suite software. Ask other software vendors for their preferred benchmark application.

Download ETBenchmark

Make sure you're always running the latest version of the ETBenchmark.exe.

  • Download ETBenchmark.exe
  • Place this application on your SERVER in the shared Execu/Tech software folder!
    DO NOT place this file on the CLIENT COMPUTER. The results will be invalid.

How to run the Network Benchmark (ETBenchmark)

There are 2 ways to run ETBenchmark:

  1. Run from the Hotel Folder
  2. Run from the Execu/Tech Application

From the Hotel Folder

  1. On the CLIENT COMPUTER, using Windows File Explorer, browse to the shared folder on the server where the Execu/Suite software is installed.
  2. Locate ETBenchmark.exe and run it by double-clicking the application (hosted on the SERVER.)



  3. See Perform the Tests for the next steps.

From the Execu/Tech Application

  • If you have a current version of Execu/Tech, you can run the Network Benchmark from the application without having to navigate to the server.
  • At hotel PMS workstations, go to File › Special › Run Network Benchmark.

    ​​
  • At POS workstations, go to POS Administrator › System › Run Network Benchmark.
  • See Perform the Tests for the next steps.


Perform the Tests

  1. When the Network Benchmark application opens, click Test Now to begin the test.





    While the test is running, the file containing the test records will grow. Because of this, it is normal for the benchmark score to lower slowly throughout the test. It's normal and expected that the READ times will increase as the test progresses. This is because the test file gets larger as the test progresses.
  2. After the first test completes, you can select the Perform Internet Bandwidth Speed Test to test your internet connection. This isn't necessary and typically isn't an indicator of potential software performance - it's just an additional statistic.



  3. After the benchmark application has completed the test, results will be displayed, and an estimate of your expected performance will be displayed in the Test Results box.

 

 

 

​

Understanding your score


ETBenchmark Log file
When the benchmark finishes and provides a score, this score is logged in a file, ETBenchmarkLog.txt. This file is located in the same folder where the benchmark application is installed (which is typically the server.) 

  • The score represents the number of times per second that the client computer is able to open a file on the server, read it, write a single line, then save the file on the server.
  • Low scores can be a symptom of a problem that has the potential to corrupt your data and lead to critical and unrecoverable data loss.

Score Range

0-50 This is a very poor score. The software will be unusable, and you are risking data corruption.
51-75 This is a poor score. The software may be usable, but you may experience extended delays.
76-125 This is a below average score. The software may be usable, but you may experience delays.
126-200 This is a low average score. The software should be usable, but you may experience slight delays.
201-300 This is an average score. The software should be usable with few delays.
301-900 This is an above average score. The software should be usable with few delays.
901+ This is a high score. The software should be usable with few delays.

Delays



In the middle of the benchmark application, the Delays box shows you how many times it took longer than 1/10th of a second to open, read, write and save the file. Delays are normal but the more you have, the more problems you will have. A Max Duration of longer than a second or two might be an indication of deficient or failing hardware (network, hard drive, etc.)

Low Score - Most Common Causes

 

A low score can be caused by many things. Based on our experience and feedback from our customers over more than 25 years, these are the most common causes:

  • Antivirus is improperly configured. System Requirements
  • Server hardware doesn't meet our minimum requirements, found here: System Requirements.
  • Server hardware is failing.
  • Client hardware doesn't meet our minimum requirements, found here: System Requirements.
  • Client hardware is failing.
  • Network hardware doesn't meet our minimum requirements, found here: System Requirements
  • Network hardware is failing.
  • Incompatible network hardware. (Just because two brands claim the same compatibility it doesn't mean they will communicate effectively.)
  • Mix of SMB protocols.
  • Bad or old drivers.

Low scores can be a symptom of a problem that has the potential to corrupt your data and lead to critical and unrecoverable data loss.

 

It's your on-site network professional's responsibility to determine the actual cause of the problem and to find a solution.

​

Remote Desktop Services
If you're not able to invest the time and expense to diagnose and improve your network infrastructure, you might want to consider Microsoft's Remote Desktop Services. As long as your server is capable, this can alleviate issues caused by poor client computer and network performance by eliminating data handling at the client and performing nearly all application functions at the server. This also opens up the possibility of remotely accessing the Execu/Tech applications using a secure web portal.

 

How to Read ETBenchmark Results

Always be sure you're running the latest version. Download ETBenchmark.exe

 

After ETBenchmark runs, Notebad will open with the last run results. This tells you how to read those results.

 

ETBenchmark measures the type of repeated file access used by Execu/Tech applications. It is not a general internet speed test and should not be compared directly with ping, iPerf, or a large file copy. A network may show excellent bandwidth while still having poor small-file, file-locking, or SMB response times.

The examples below use anonymous computer names, server names, user names, addresses, and hardware information.

Each result is followed by a plain-language explanation. Use the measurements together rather than relying on any single value.

============================================================
ETBenchmark v.2026.7.13.2
============================================================

BENCHMARK SESSION
------------------------------------------------------------
Benchmark Started: July 13, 2026 12:19:35 PM
Benchmark Stopped: July 13, 2026 12:20:58 PM
Records Tested: 5000
Run From Folder: \\FILESERVER\Application

BENCHMARK RESULTS
------------------------------------------------------------
Score: 366
Score Comment: This is an above average score. The software should be usable with few delays.
Avg Read Time (ms): 10.14
Max Read Time (ms): 127.6
Avg Write Time (ms): 6.16
Max Write Time (ms): 99.27
Delays: 0
Maximum ETBenchmark Process I/O Rate (Mbps): 342.44

NETWORK INFORMATION
------------------------------------------------------------
Resolved Path: \\FILESERVER\Application
Network Server: FILESERVER
Server Address: 192.168.10.20
Local IP Address: 192.168.10.45
Connection Type: Wired Ethernet
Network Adapter: Ethernet Adapter
Adapter Name: Ethernet
Adapter Status: Up
Link Speed: 1 Gbps
Network Interface: Ethernet
MAC Address: 00-11-22-33-44-55
Interface Index: 11
DHCP Enabled: True
Default Gateway: 192.168.10.1
DNS Servers: 192.168.10.20, 192.168.10.21

COMPUTER INFORMATION
------------------------------------------------------------
Windows User: USER
Computer Name: WORKSTATION01
Windows Version: Microsoft Windows 11 Pro
Screen Resolution: 1920 X 1080
CPU: Example Processor 2.40GHz 2400 Mhz,
Total RAM: 31.8GB
Available Ram: 14.4GB
CPU Usage: 34.8 %

* * * Additional Network and File Diagnostics * * *
Diagnostic Path: \\FILESERVER\Application
Resolved Path: \\FILESERVER\Application
Path Type: Network
Network Server: FILESERVER
Server Address: 192.168.10.20
DNS Lookup Time: 0.433 ms
Ping Samples Sent: 25
Ping Samples Received: 25
Ping Samples Lost: 0
Ping Packet Loss: 0%
Ping Samples: 25
Ping Minimum: 4 ms
Ping Average: 5.68 ms
Ping Maximum: 31 ms
Ping P50: 5 ms
Ping P95: 5 ms
Ping P99: 31 ms
SMB Port 445: Available
SMB Connection Samples: 5
SMB Connection Minimum: 5.49 ms
SMB Connection Average: 6.393 ms
SMB Connection Maximum: 7.695 ms
SMB Connection P50: 5.821 ms
SMB Connection P95: 7.695 ms
SMB Connection P99: 7.695 ms
File Create Samples: 25
File Create Minimum: 3.9 ms
File Create Average: 4.625 ms
File Create Maximum: 5.821 ms
File Create P50: 4.503 ms
File Create P95: 5.634 ms
File Create P99: 5.821 ms
File Open Samples: 25
File Open Minimum: 1.004 ms
File Open Average: 1.317 ms
File Open Maximum: 1.926 ms
File Open P50: 1.283 ms
File Open P95: 1.736 ms
File Open P99: 1.926 ms
File Close Samples: 25
File Close Minimum: 0.021 ms
File Close Average: 0.029 ms
File Close Maximum: 0.055 ms
File Close P50: 0.024 ms
File Close P95: 0.05 ms
File Close P99: 0.055 ms
File Rename Samples: 25
File Rename Minimum: 6.578 ms
File Rename Average: 7.717 ms
File Rename Maximum: 10.757 ms
File Rename P50: 7.654 ms
File Rename P95: 9.773 ms
File Rename P99: 10.757 ms
File Delete Samples: 25
File Delete Minimum: 2.633 ms
File Delete Average: 3.231 ms
File Delete Maximum: 3.851 ms
File Delete P50: 3.197 ms
File Delete P95: 3.798 ms
File Delete P99: 3.851 ms

============================================================
END OF ETBENCHMARK RESULTS
============================================================
Result Example How to Read It
Benchmark Started / Stopped July 13, 2026 12:19:35 PM / 12:20:58 PM Shows when the test ran and how long the test lasted.
  • Use these times to compare the benchmark with server, switch, firewall, antivirus, and Windows event logs.
Records Tested 5000 of 5000 Shows whether the benchmark completed its full test workload.
  • Results from an early-stopped test may still be useful, but a completed test is more reliable.
Run From Folder \\FILESERVER\Application Shows the exact folder being tested.
  • The benchmark should normally be run from the same network location used by the application.
Score 366 A summary of the overall per second record-processing rate during the test.
  • Higher is better. The score should be considered together with read, write, delay, ping, and file-operation statistics.
Score Comment Above average A general interpretation of the score based on typical application performance.
  • This is a usability guideline, not a diagnosis of the exact cause of a performance issue.
Average Read Time 10.14 ms The average time required to read the benchmark file.
  • Lower is better. A low average with a very high maximum can still indicate intermittent freezes.
Maximum Read Time 127.6 ms The slowest individual read recorded during the benchmark.
  • Large spikes may indicate SMB delays, storage latency, antivirus scanning, wireless interference, or server load.
Average Write Time 6.16 ms The average time required to append data to the benchmark file.
  • Consistently high write times may point to storage, SMB, security software, or server-side contention.
Maximum Write Time 99.27 ms The slowest individual write recorded during the benchmark.
  • This is useful for identifying brief stalls that may not be visible in the average.
Delays 0 Counts longer pauses detected during the benchmark.
  • Repeated delays are often more important to user experience than raw bandwidth.
Maximum ETBenchmark Process I/O Rate 342.44 Mbps The highest rate at which ETBenchmark itself was reading and writing data during the test.
  • This measures ETBenchmark’s own file activity. It is not a test of the workstation’s total network speed and should not be compared directly with iPerf or link speed.
Resolved Path \\FILESERVER\Application Shows the network path after resolving a mapped drive, when possible.
  • This helps confirm which server and share are actually being tested.
Network Server FILESERVER The server hosting the tested folder.
  • Use this name when comparing the benchmark with server logs or monitoring tools.
Server Address 192.168.10.20 The IP address resolved for the file server.
  • Confirms which server address the workstation is using.
Local IP Address 192.168.10.45 The workstation address used to reach the server.
  • Useful for identifying routing, subnet, VPN, and adapter-selection issues.
Connection Type Wired Ethernet Shows whether Windows is using wired Ethernet, Wi-Fi, VPN, or another interface.
  • This is based on the adapter Windows uses to reach the server, not simply which adapters are enabled.
Network Adapter / Adapter Name Ethernet Adapter / Ethernet Identifies the exact network interface used for the connection.
  • Virtual adapters, docks, USB adapters, VPNs, and Wi-Fi may affect performance differently.
Adapter Status Up Shows whether Windows reports the selected adapter as operational.
  • An Up status does not prove the connection is performing correctly; it only shows that the adapter is active.
Link Speed 1 Gbps The negotiated speed reported by the network adapter.
  • Link speed is capacity, not proof of good file I/O. A 1 Gbps connection can still have poor SMB response times.
DHCP Enabled True Shows whether the workstation received its IP settings through DHCP.
  • This is informational and may help identify incorrect or unexpected network configuration.
Default Gateway 192.168.10.1 The gateway assigned to the selected network adapter.
  • A gateway is normally not used when the workstation and server are on the same subnet.
DNS Servers 192.168.10.20, 192.168.10.21 The DNS servers assigned to the selected adapter.
  • Slow or incorrect DNS can delay name resolution, although it does not normally explain slow file I/O after a connection is established.
CPU Usage 34.8% The workstation CPU usage near the end of the test.
  • Very high CPU use may affect benchmark results, but a normal CPU value does not rule out network or storage problems.
Available RAM 14.4 GB The physical memory available on the workstation.
  • Low available memory may cause paging and pauses that can resemble network problems.
DNS Lookup Time 0.433 ms The time required to resolve the server name to an IP address.
  • This should normally be very small on a local network. High or inconsistent values may indicate DNS problems.
Ping Samples Sent / Received / Lost 25 / 25 / 0 Shows basic packet delivery between the workstation and server.
  • Packet loss is not expected on a healthy local network. Even small amounts of loss can cause noticeable SMB delays.
Ping Minimum / Average / Maximum 4 ms / 5.68 ms / 31 ms Shows the range of round-trip network latency.
  • For a local wired network, consistently low values are expected. Spikes are often more important than the average.
Ping P50 / P95 / P99 5 ms / 5 ms / 31 ms Shows typical and worst-case ping behavior across the sample set.
  • P50 is the median. P95 means 95% of samples were at or below that value. P99 highlights near-worst-case latency.
SMB Port 445 Available Shows whether the workstation can establish an SMB connection to the file server.
  • This verifies basic SMB reachability, not the speed of file operations.
SMB Connection Minimum / Average / Maximum 5.49 ms / 6.393 ms / 7.695 ms Shows how quickly a connection to SMB port 445 can be established.
  • High or inconsistent values may indicate routing, firewall, endpoint security, or server response delays.
File Create Average 4.625 ms Measures the time required to create a new small file in the tested folder.
  • This exercises SMB metadata, permissions, directory updates, antivirus, and server storage.
File Open Average 1.317 ms Measures the time required to open an existing file.
  • Slow file-open performance can directly affect record-oriented and multi-file applications.
File Close Average 0.029 ms Measures the time required to close the test file handle.
  • Close times are often very small, but large spikes may still indicate flushing or security-software delays.
File Rename Average 7.717 ms, Maximum 10.757 ms Measures the time required to rename a file in the tested folder.
  • A large maximum with a much lower median suggests an intermittent stall. Antivirus, indexing, backup, or server storage may contribute.
File Delete Average 3.231 ms Measures the time required to delete a file from the tested folder.
  • Delete performance is another SMB metadata test and may be affected by permissions, security software, or storage latency.
Minimum Lowest measured value The fastest individual sample.
  • Minimum values show best-case performance and should not be used alone to judge overall behavior.
Average Mean of all samples The overall average response time.
  • Averages can hide brief but severe stalls.
Maximum Highest measured value The slowest individual sample.
  • A high maximum may reveal the pauses users experience as freezing or locking.
P50 Median Half of the samples were at or below this value.
  • P50 represents typical performance better than the minimum.
P95 95th percentile 95% of samples were at or below this value.
  • P95 is useful for identifying recurring slow operations without letting one isolated spike dominate the result.
P99 99th percentile 99% of samples were at or below this value.
  • P99 highlights near-worst-case performance and is useful for finding intermittent application stalls.

Important Notes

A successful ping or iPerf test does not prove that Windows file access is performing correctly. Ping measures small-packet round-trip latency. iPerf measures large-block network throughput. ETBenchmark measures repeated SMB and file operations that more closely resemble the workload used by Execu/Tech applications.

When troubleshooting, compare the affected workstation with a known-good workstation using the same server, share, switch, application folder, and benchmark version. The most useful signs of a problem are packet loss, high maximum values, large differences between P50 and P95/P99, repeated delays, and file-operation times that are much worse on one workstation than another.


Related Pages:

 

Cobol File Errors
Slow / Stuck Software
Rebuild Corrupted File
Common System Issues





Article ID
 network_benchmark
Views
 5917
Last Modified
 7/13/2026 12:30 PM