A few of my friends asked me to assist them with getting up to speed with SLOB2 testings. I have decided to publish this quick blog post and give people to a few hints.
Here are some of the scripts I have used to simplify SLOB testing management for my testing efforts:
Physical IO testing
Logical IO testing
Quick tests verification
- For LIO testing: the starting point could be LIOPS and CPU time in TOP 5 Events section. LIOPS should be ~700-800k per CPU/Process, CPU should be 99% from the TOP Events. If one of the parameters doesn’t reflect expected values, then something may be wrong.
- For PIO “db file sequential read” must be in the range ~98-99.999%. If not you should fix possible issues and rerun the tests
One last warning: for some of you it could be obvious, but I have missed it during the first few runs and lost a bit of testing time because of the issue. Check cr_tab_and_load.out file each time you run ./setup.sh to create new test data. Kevin put a warning in the setup.sh. Do not ignore it!
The ./setup.sh script have the following message: NOTIFY: ./setup.sh: Loading procedure complete (130 seconds). Please check ./cr_tab_and_load.out for any errors
You may not be testing what you think you are.
Interested in working with Yury? Schedule a tech call.