ooibc88 / blockbench

BLOCKBENCH: A Framework for Analyzing Private Blockchains. Blockbench contains workloads for measuring the data processing performance, and workloads for understanding the performance of different layers of Blockchain systems.
https://www.comp.nus.edu.sg/~dbsystem/fabricsharp/#/blockbench
Apache License 2.0
391 stars 174 forks source link

The result return zero in ethereum kvstore #56

Open yuexk opened 5 years ago

yuexk commented 5 years ago

I running the Ethereum benchmark for kvstore and return the zero result, why? How to solve??

yuexk commented 5 years ago

to address: 0x4d0e20f9887846285347dda39f8598057ef22c72 Smart contract ycsb deploy ready Current TIP = 35 In the last 2s, tx count = 0 latency = 0 outstanding request = 4 In the last 2s, tx count = 0 latency = 0 outstanding request = 142 In the last 2s, tx count = 0 latency = 0 outstanding request = 244 In the last 2s, tx count = 0 latency = 0 outstanding request = 295 In the last 2s, tx count = 0 latency = 0 outstanding request = 362 In the last 2s, tx count = 0 latency = 0 outstanding request = 407 In the last 2s, tx count = 0 latency = 0 outstanding request = 476 In the last 2s, tx count = 0 latency = 0 outstanding request = 544 In the last 2s, tx count = 0 latency = 0 outstanding request = 690 In the last 2s, tx count = 0 latency = 0 outstanding request = 836 In the last 2s, tx count = 0 latency = 0 outstanding request = 984 In the last 2s, tx count = 0 latency = 0 outstanding request = 1132 In the last 2s, tx count = 0 latency = 0 outstanding request = 1262 In the last 2s, tx count = 0 latency = 0 outstanding request = 1403 In the last 2s, tx count = 0 latency = 0 outstanding request = 1545 In the last 2s, tx count = 0 latency = 0 outstanding request = 1668 In the last 2s, tx count = 0 latency = 0 outstanding request = 1805

I running the command run-bench.sh 8 8 8 128 in ethereum benchmark and the driver is kvstore driver

yolo-612 commented 5 years ago

Hello, do you have to deploy smart contracts yourself? I also got the similar result

to address: Failed to query. Smart contract ycsb deploy ready Current TIP = -1 In the last 2s, tx count = 0 latency = 0 outstanding request = 1 In the last 2s, tx count = 0 latency = 0 outstanding request = 1 In the last 2s, tx count = 0 latency = 0 outstanding request = 1 In the last 2s, tx count = 0 latency = 0 outstanding request = 1 In the last 2s, tx count = 0 latency = 0 outstanding request = 1 In the last 2s, tx count = 0 latency = 0 outstanding request = 1

I don't have an address. Is it because the smart contract is not deployed?

talent-nansy commented 3 years ago

I have met the same problem when testing fabric v2.2 version. And I have tried to change the command line into ./driver -db fabric-v2.2 -threads 1 -P workloads/workloada.spec -txrate 5 -endpoint localhost:8800,localhost:8801,localhost:8802 -wl ycsb -wt 20 in which specify the 3 endpoints.

tienquyet28 commented 1 year ago

Hello, do you have to deploy smart contracts yourself? I also got the similar result

to address: Failed to query. Smart contract ycsb deploy ready Current TIP = -1 In the last 2s, tx count = 0 latency = 0 outstanding request = 1 In the last 2s, tx count = 0 latency = 0 outstanding request = 1 In the last 2s, tx count = 0 latency = 0 outstanding request = 1 In the last 2s, tx count = 0 latency = 0 outstanding request = 1 In the last 2s, tx count = 0 latency = 0 outstanding request = 1 In the last 2s, tx count = 0 latency = 0 outstanding request = 1

I don't have an address. Is it because the smart contract is not deployed?

i have met same problem when try to debug the own execute with ./driver it cannot find to address: cannot connect to server

tienquyet28 commented 1 year ago

can anyone help please? thanks so much