EOSBenchTool is a free, open source client-side utility for measuring how an EOS node performs under load. It is aimed at developers, node operators and blockchain testers who want repeatable numbers instead of guesses. The project is licensed under LGPL and offers a Windows build or installer, with macOS and Linux builds also available. Results depend heavily on the node and hardware you point it at.
Before you start, note that the project is no longer actively maintained. Its last code update was in September 2018, so it may not match newer EOS releases. Treat it as a reference tool for understanding the testing approach rather than a current, actively developed product.
What Is EOSBenchTool and Who Is It For?
EOSBenchTool connects to an EOS node, sends it transactions and shows how the node responds to a chosen load. It does not run a blockchain itself. It is most useful for people who already work with EOS and need a repeatable way to measure their setup.
The likely readers are EOS developers who want to know how their application's transaction volume will behave, and node operators comparing hardware or configuration changes. QA engineers building test environments for EOS projects can also use it as a starting point. Beginners will find the setup more demanding, so learning the basics of the network first helps.
How Client-Side Load Testing Works on EOS
Load testing on a blockchain means generating many transactions and watching how the network processes them. The client creates and submits transactions at a chosen rate, while the node does the actual processing. Measuring from the client keeps the test close to how a real application would behave.
The project's own examples use cleos, the EOS command-line tool. They point commands at a local node on port 8888, deploy the eosio.token contract, create a token and issue supply to an account. That gives you a controlled test chain with known state, which makes it easier to tell whether a slowdown comes from your settings or from unrelated changes.
Two terms matter here. The transaction pool holds transactions waiting to be sent, and throughput describes how many transactions complete in a given time window.
Practical Scenarios for Testing an EOS Setup
Teams use a tool like this in a few common ways. Each one works best when you change only one or two settings at a time.
- Comparing two machines: run the same host address, thread count and batch size on a laptop and a server, then compare the results.
- Choosing a thread count: start at your CPU count and test higher and lower values to see where extra threads stop helping.
- Checking a test chain before a change: run the pool and batch settings you expect to use against a local chain first.
Record each configuration and rerun the test whenever something changes, so results stay comparable across sessions.
Key features
Host address
Thread number
Transaction pool size and total tokens
Transaction batch size
Supported coins
EOSBenchTool is built around the EOS blockchain. Its examples work with the eosio.token contract and generate test activity against the EOS node you connect to. Because its focus is EOS, it is not a tool for testing other blockchains.
How to install EOSBenchTool on Windows
- 1
Get the Program from the Official Source
Download only from the official project page on GitHub at github.com/OracleChain/EOSBenchTool, using the Releases page. The project offers a Windows build or installer, so choose the Windows option listed there.
- 2
Verify the File
Before running anything, check whether the release lists a SHA-256 checksum or signature, and compare it with your downloaded file. Do not run the file if the values do not match.
-
Install and Launch
Run the installer, or unpack the Windows build into a folder of your choice, then start the program. Make sure the EOS node you plan to test is running and reachable before you enter its address.
System requirements
- Thread number: set it to your computer's CPU count, as the project recommends
- A running EOS node reachable at the host address you configure
- Windows build or installer available; macOS and Linux builds are also offered
How to use EOSBenchTool
Once the program is installed, a test run comes down to a few settings. Change one variable at a time so you can tell which change affected the results.
- Enter the host address of the EOS node you want to test.
- Set the thread number to your computer's CPU count as a baseline.
- Choose the transaction pool size and total tokens for the run.
- Set the transaction batch size, starting with a moderate value.
- Start the test, record the results, then repeat with one setting changed.
Keep a simple log of each run that includes the settings and the node version. Comparing logs side by side is the fastest way to see which change mattered.
Pros & cons
- Free and open source under the LGPL license
- Windows build or installer available, plus macOS and Linux builds
- Four adjustable settings: host address, threads, pool and batch size
- Focused on EOS, so every setting maps directly to node testing
- No code updates since 2018, so compatibility with newer EOS releases is uncertain
- Works only with EOS, not as a general-purpose tool
- Requires a separately running EOS node and some command-line comfort
- Setup examples rely on cleos and other command-line steps
Is EOSBenchTool safe?
EOSBenchTool is open source under LGPL, and its code is public on GitHub, so you can review it yourself. Get it only from the official GitHub repository or its Releases page, not from mirror sites or file aggregators. If a SHA-256 checksum or signature is published for the version you choose, verify it before running the installer. The project has had no code updates since 2018, so issues found after that date may never be fixed. Check the latest version on the official website, and run the tool against a test chain rather than a production node. The program does not manage wallets or private keys, and no legitimate tool should ever ask for a seed phrase.
- Official source only. Download from github.com/OracleChain/EOSBenchTool. Ignore ads and lookalike domains.
- Check the SHA-256. Compare the installer hash with the value the developer publishes before running it.
- Never share your seed phrase. No developer, support agent or website — including CryptApps — will ever ask for it.
Alternatives
EOSBenchTool sits in a different place than most programs in this category. Geth, Nethermind and Bitcoin Core are full clients that run and sync their own blockchains. Agave is a Solana validator, and TON and Aptos offer node and CLI tools for their own networks. EOSBenchTool does not run a node for you. Its job is to generate load and measure how an EOS node responds. If you need a node for another network, choose that network's client, and if you want to test EOS node performance, EOSBenchTool is the direct match.
Specifications
- Price
- Free
- Type
- Open source
- License
- LGPL
- Latest version
- dawn-4.2
- Last update
- 27 Sept 2018
- Windows support
- Yes (Windows build or installer)
- Source code
- github.com/OracleChain/EOSBenchTool
Frequently asked questions
Yes. EOSBenchTool is free and open source under the LGPL license, and its source code is published on GitHub. You do not need to pay to download or run it. Read the license text in the repository if you plan to share modified copies.
It can be, if you get it from the official GitHub repository and verify the file. Because the code is open, you can inspect it. Keep in mind that the project has had no updates since 2018, so test it on a non-production system first.
Not recently. The last code update was on September 27, 2018, and the latest version is dawn-4.2. Because of that gap, it may not match newer EOS releases, so confirm compatibility with your node version before trusting the results.
Yes. The tool sends test traffic to an EOS node through the host address you enter, so the node must be running and reachable. Many users start with a local test chain, which keeps live networks unaffected while they learn the settings.
The thread number controls how many parallel workers the tool uses. The project recommends setting it to your computer's CPU count. Going far beyond that can make your own machine the bottleneck, which skews the measurements.
No. EOSBenchTool is built for performance testing, not for managing funds or everyday accounts. It generates activity against an EOS node so you can measure how that node responds.
The project lists macOS and Linux among its platforms, in addition to Windows. This page focuses on the Windows build, but the same settings apply on each system. If you test on several operating systems, keep the settings identical so the results stay comparable.
Verdict
EOSBenchTool is a narrow, free tool for one job: measuring how an EOS node handles transaction load from a Windows computer. It suits EOS developers and node operators who want to experiment with host, thread, pool and batch settings. Because the project has been dormant since 2018, it works better for learning and reference than for critical production decisions. If you need current tooling, look for newer options and use this one to understand the testing approach.