Forum Discussion
Hi,
VirtActions are specific to resource paths to handle requests and responses from a Virt and not server load. You will need to make a change to the Virt to handle server load by adjusting the server capacity settings for the Virt. Please see the below link for more details.
https://support.smartbear.com/readyapi/docs/virtualization/configure/behavior.html
Regards,
Marcus James
SmartBear Support
- rahuldutta4 years agoOccasional Contributor
Hi,
Thanks for your reply. I have already updated the min and max threads to XL and above in the behavior settings but still the service is unable to scale beyond 250 tps. It is probably because of the complex condition checks in the Dispatch script. Below are my VM configurations, which I believe are sufficient to allow more number of threads.
- AlexKaras4 years agoChampion Level 3
Hi,
Out of curiosity: what is the reason to *load test* *virtual* service?
- nmrao4 years agoChampion Level 3I agree with Alex. I don't see any point running the load or performance test. Virtual server is basically to enable QA team to create the test cases or automation while the dev team actually develop the service.
Related Content
- 11 months ago
- 14 years ago
- 2 years ago