用loadrunner测试webservices的东西时，报错：Abnormal termination, caused by mdrv process termination。
网上找的答案资料：
Hi, Users facing this mdrv process abnormal termination can try one of these options found from one of the LR articles. The Loadrunner vusers are run by a process called 'mdrv.exe'. Whenever this process encounters errors due to various reasons it may terminate. Some of the possible reasons are as follows.
解决方法：
• The Host machine ( Load generator) is running too many Vusers as a result of which it system resources are being maximized. ( i.e. Consistent over 90% CPU and Memory utilization). The mdrv process does not get enough resources to process the request as a result it fails
• If you have Custom C coding, there is a possibility of allocated memory not being freed or memory violation errors which can lead to 'mdrv process termination'.
• Replay the script. with think time.
• Turn off extended log when running the script. in the controller.
• Do not use the controller itself as the loadgenerator. i.e. have a remote LoadGenerator.
• Introduce iteration pacing, if running more than one iteration each vuser.
• Open the file C:\WinNT\wlrun7.ini in a text editor, modify the entry from: AgentMaxThreadsPerDriver=50 to AgentMaxThreadsPerDriver=20 or 10
• Run Agent as process instead of service Launch command prompt and navigate to C:\Program Files\Mercury\Loadrunner\Launch_service\bin and run the command magentserive -remove. This will remove the agent. Now run the command magentproc -install This will install the agent as a process.
• Run vusers as process instead of threads.Please go to Runtime Settings > Miscellaneous > Multithreading > RunVuser as a process.
太多条，设了几个都不好使，后来仔细想了想脚本有么有问题，发现调用服务时，controller的迭代设置是连续发送，可能是服务器接受回应速度慢，导致多线程并发时，mdrv进程死掉了，不是特别理解。有待提高。
后来把pacing设置成固定时间间隔，不断调整时间，从5秒，1秒，0.1秒，0.01秒后来错误就消失了，但是TPS变小了。所以需要根据业务来确定。
真正学好LR和性能测试也不是易事，继续努力，和朋友们共同学习！
