lcabaceira
commented
8 years ago Actually we will not have more tests. 400Mb tests the IO considering the disk/OS caches because the file is relatively small. Then the other file is 8GB specifically to avoid the usage of caches.
So i think you are confusing 8GB with 800MB.
Hi all,
About the import files on the I/O tests, I would like to share a thought.
According to Luis's last task (and to my request on it), the file names have been changed as described below.
io-test-plan.indexes.400mb.json io-test-plan.content.400mb.json io-test-plan.indexes.8gb.json io-test-plan.content.8gb.json
It looks good but an improvement could be possibile:
To make everything compliance with the ETLs and correctly presented in the dashboards, I suggest two modifications below.
1) Change the file names as described below: io-test-plan.indexes.TIMESTAMP.json (TIMESTAMP is a unique value to distinguish the data flow) io-test-plan.content.TIMESTAMP.json (This is a different TIMESTAMP value compared with the one introduced above) (for the goal of this purpose, also two files named io-test-plan.TIMESTAMP.json will be fine)
2) Change the "ExecutionPlan" description into the json files to reduce the length (this will be better for the dashboard) and better describe the tests. I suggest: "Execution Plan":"Content Store FS for 400Mb" (case: 400mb io test on content store) "Execution Plan":"Indexes FS for 400Mb" (case: 400mb io test on indexes) "Execution Plan":"Content Store FS for 800Mb" (case: 800mb io test on content store) "Execution Plan":"Indexes FS for 800Mb" (case: 800mb io test on indexes)
If the two changes will be accepted, no actions are required from the ETLs/dashboards side (tests apart).
I assign to Luis this task, waiting for a reply and take a decision together.
Cheers.