kevinherron / stack-bench

Simple OPC UA stack benchmarking tool

Building

mvn clean package

Running

Start a server to test against and make sure it has a .conf entry in the configs directory.

Then run: java -jar target/stack-bench-$version.jar configs/$config.conf

Results

Benchmark performed on Intel Core i7-6700K running Fedora 24, kernel 4.7.9, Oracle Java 8u101

Throughput, SecurityPolicy=None

Stack	Concurrency=1	C=4	C=16	C=64	C=128
Eclipse Milo	7599 req/s	23626 req/s	28867 req/s	27979 req/s	29085 req/s
Prosys/OPC Foundation	2784 req/s	6298 req/s	8507 req/s	10515 req/s	11842 req/s
node-opcua	743 req/s	1024 req/s	1038 req/s	1042 req/s	1034 req/s
Unified Automation C++	6451 req/s	18894 req/s	21830 req/s	20827 req/s	20095 req/s

stack-bench's Issues

Each connection establishment will be done at localhost

Regardlessly which address is entered into the config file (e.g. "opc.tcp://10.11.5.8:51210/UA/Server"), the client will connect to "opc.tcp://localhost:51210/UA/Server". This is caused by function "getOpcUaClient(endpointUrl: String)". Variable 'endpointUrl' contains the correct string from the config file, after UaTcpStackClient.getEndpoints(endpointUrl).get() the IP address in variable 'endpoints' will be replaced and the client tries to connect to the localhost.

If the server certificate is modified with the current fix IP address the stack-bench tool will work.