Closed javenleee closed 8 months ago
Looks like some workers are not terminating which is odd. A couple of things to try.
--caliper-logging-targets-file-enabled true
this should generate caliper.log files with hopefully more informationLooks like some workers are not terminating which is odd. A couple of things to try.
- Generate a caliper debug log. Add the following option when you launch the caliper manager and caliper workers (if you are using seperate remote workers)
--caliper-logging-targets-file-enabled true
this should generate caliper.log files with hopefully more information- Check the resource utilisation on the machine that you are running caliper. You could very well be running out of resource such as CPU/Memory which will have an impact. In order to properly benchmark a fabric network you should not have caliper and fabric on the same machine as they both contend for physical resource which could skew results
Thank you for your response. I attempted to review the output logs, which consist of approximately 29,000 lines. While examining the latest portion, I didn't find any evident error logs, only some more detailed information.
[process-messenger] Process "10862" handling message: {"sender":"10888","recipients":["10862"],"type":"testResult","content":{"subCollectors" :[],"active":false,"stats":{"metadata":{"workerIndex":4,"roundIndex":1,"roundLabel":"Change car owner.","roundStartTime":1705406186789,"roundFinishTime":1705406195778},"txCounters":{"totalSubmitted ":100,"totalFinished":100,"totalSuccessful":34,"totalFailed":66},"timestamps":{"firstCreateTime":1705406186792,"lastCreateTime":1705406193670,"firstFinishTime":1705406186913,"lastFinishTime":170540 6195689},"latency":{"successful":{"min":71,"max":2041,"total":14295},"failed":{"min":34,"max":2019,"total":24972}}},"type":"txUpdate"},"date":"2024-01-16T11:56:36.781Z"}
Additionally, I examined the utilization of my system resources. Fortunately, throughout the entire process, the system resource usage did not exceed 30%.
There may not be any error messages, but maybe the logs can show differences between a worker that completed successfully and one that did not ? The above looks like it indicates worker 4 completed successfully. I must admit I've never really used the tx counter for rounds, I've always used duration and I'm not even sure caliper can guarantee the exact amount of transactions will be sent.
There may not be any error messages, but maybe the logs can show differences between a worker that completed successfully and one that did not ? The above looks like it indicates worker 4 completed successfully. I must admit I've never really used the tx counter for rounds, I've always used duration and I'm not even sure caliper can guarantee the exact amount of transactions will be sent.
After conducting multiple tests, I indeed discovered that my CPU was being fully utilized. I will attempt to run Caliper and Fabric separately. Once again, thank you for your suggestions.
This time I set the block size to 1, tps to 5 and only one worker, I'm sure that I didn't run out of cpu this time, but this problem came back, I don't know what's the reason for it
There may not be any error messages, but maybe the logs can show differences between a worker that completed successfully and one that did not ? The above looks like it indicates worker 4 completed successfully. I must admit I've never really used the tx counter for rounds, I've always used duration and I'm not even sure caliper can guarantee the exact amount of transactions will be sent.
Which Caliper version are you using?
0.5.0
Which Node.JS version are you using?
v16.20.2
Which operating system are you using?
Ubuntu 20.04
Please provide some context for your error. For example, when did the error occur? What were you trying to achieve, and how?
I'm conducting performance testing on my Hyperledger Fabric network using Caliper. However, I encountered the following issue when the transactions per second (TPS) reached a relatively high level, around 110:
actually, in my orderer's log, there are 808 tx(it is 1000 in my config file) it has ordered. so i think there are still about 200 tx which has not been launched and the caliper is just stuck here
What was the observed incorrect behavior?
The logs persistently display the same content:
with no signs of progress.
Please provide the error logs and their surroundings.
Please provide any additional information you deem relevant to the error.
No response