New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Azure cache #10171
Azure cache #10171
Conversation
Also: Added additional debug logging to AzureBlobDisk. Removed MD5 check in AzureBlobDisk - it's not needed.
@chessbyte @Fryguy @hsong-rh - Please review. |
@chessbyte - the cassette files submitted with PR may not apply to Darga. We'll probably have to cherry-pick the commit for the code changes, and rerecord the cassettes for Darga. |
@bdunne Would it be possible to avoid yml files in the content checker for the bot? See the results here. |
<github_pr_commenter_batch />Some comments on commits roliveri/manageiq@6c27d6e~...31d54e1 gems/pending/spec/recordings/miq_vm/miq_azure_vm_image_spec/miq_azure_vm_image_spec_rootTrees-1.yml
gems/pending/spec/recordings/miq_vm/miq_azure_vm_image_spec/miq_azure_vm_image_spec_rootTrees-2.yml
gems/pending/spec/recordings/miq_vm/miq_azure_vm_image_spec/miq_azure_vm_image_spec_rootTrees-3.yml
gems/pending/spec/recordings/miq_vm/miq_azure_vm_image_spec/miq_azure_vm_image_spec_rootTrees-4.yml
gems/pending/spec/recordings/miq_vm/miq_azure_vm_image_spec/miq_azure_vm_image_spec_rootTrees-5.yml
gems/pending/spec/recordings/miq_vm/miq_azure_vm_image_spec/miq_azure_vm_image_spec_rootTrees-6.yml
gems/pending/spec/recordings/miq_vm/miq_azure_vm_image_spec/miq_azure_vm_image_spec_rootTrees-7.yml
gems/pending/spec/recordings/miq_vm/miq_azure_vm_instance_spec/miq_azure_vm_instance_spec_rootTrees-1.yml
gems/pending/spec/recordings/miq_vm/miq_azure_vm_instance_spec/miq_azure_vm_instance_spec_rootTrees-2.yml
gems/pending/spec/recordings/miq_vm/miq_azure_vm_instance_spec/miq_azure_vm_instance_spec_rootTrees-3.yml
gems/pending/spec/recordings/miq_vm/miq_azure_vm_instance_spec/miq_azure_vm_instance_spec_rootTrees-4.yml
gems/pending/spec/recordings/miq_vm/miq_azure_vm_instance_spec/miq_azure_vm_instance_spec_rootTrees-5.yml
gems/pending/spec/recordings/miq_vm/miq_azure_vm_instance_spec/miq_azure_vm_instance_spec_rootTrees-6.yml
gems/pending/spec/recordings/miq_vm/miq_azure_vm_instance_spec/miq_azure_vm_instance_spec_rootTrees-7.yml
|
Checked commits roliveri/manageiq@6c27d6e~...31d54e1 with ruby 2.2.5, rubocop 0.37.2, and haml-lint 0.16.1 |
@Fryguy - ping. |
|
Darga cherry-pick merge conflict:
|
@chessbyte Right. See my comment above in the original PR. The cassette files (in their own commit) don't apply to Darga because they're based on a version of azure-armrest that's not used by Darga. The commits for the code changes can be cherry-picked, but the cassette yaml files will need to be re-recorded in the Darga environment. I can re-record the cassettes, but I'm not sure how to get them into Darga with the code changes. Can we make a PR for the Darga branch that contains the code commits of this PR and a new commit for the Darga-specific cassette files? /cc @Fryguy |
Backported to Darga via #10752 $ git log
commit bb6cb2fc9f62b6e1f85126e53ab3fd3833bd9185
Merge: e8dcd99 cf07b6f
Author: Oleg Barenboim <chessbyte@gmail.com>
Date: Tue Aug 30 10:55:29 2016 -0400
Merge pull request #10752 from roliveri/darga_azure_cache
[DARGA] azure cache |
Purpose or Intent
Currently, SSA on Azure does not cache any disk IO. This results in many more IO requests made through the Azure API, than needed. Not only does this impact performance, it is prone to failure because Azure limits the number of IO requests made per hour.
This PR uses the
MiqDiskCache
module to provide disk IO caching for Azure SSA. Results show that the number of read requests per scan goes from over 7000 (un-cached) to less than 1000 (cached) - for a cross section of sample VMs. Also, scan times go from > 20 min to < 4 min in many cases.