Why Is No Data Displayed in the Real-Time Report After a Pressure Test Task Is Started?
A communication problem may exist between the debugging node and execution node used for the pressure test. The execution node reports data through port 62000 to the debugging node. Therefore, if you use customized security group rules, ensure that port 62000 of the debugging node is enabled in the security group.
You can set security group rules in Elastic Cloud Server (ECS).
Pressure Test Report Management FAQs
- Is the TPS in the Analysis Report of CodeArtsPerfTest Calculated in the Same Way as That in Other Test Tools?
- Why Is No Data Displayed in the Real-Time Report After a Pressure Test Task Is Started?
- What Are the Differences Between RPS and TPS in the CodeArtsPerfTest Report?
- What Does "AWs Without Pressure Test Data Will Be Determined As Failed" Mean in Task Logs?
- Why Does the Request Log Contain "Timeout" in the CodeArtsPerfTest Report?
- Why Does the Log Contain "Look up XXX Timeout" in the CodeArtsPerfTest Report?
- Why Does the Log Contain "Not Look Like a TLS Handshake" in the CodeArtsPerfTest Report?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore