Bug 1186763
Summary: | [scale] GetStorageConnectionsByStorageTypeAndStatus generate slow query | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Eldad Marciano <emarcian> | ||||
Component: | ovirt-engine | Assignee: | Barak <bazulay> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Eldad Marciano <emarcian> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 3.5.0 | CC: | amureini, emarcian, gklein, lpeer, lsurette, oourfali, pstehlik, rbalakri, Rhev-m-bugs, srevivo, ykaul | ||||
Target Milestone: | ovirt-3.6.0-rc | ||||||
Target Release: | 3.6.0 | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-04-20 01:31:00 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | 1097160, 1141543 | ||||||
Bug Blocks: | |||||||
Attachments: |
|
Description
Eldad Marciano
2015-01-28 13:50:42 UTC
looks like this part is taken to much time: SELECT storage_server_connections.* FROM storage_server_connections INNER JOIN storage_domains ON storage_server_connections.id = storage_domains.storage WHERE (storage_domains.storage_pool_id = '6b588963-6490-4093-a778-699094c0b07b' AND storage_domains.status = any('{0,3,4}')) this bug might depends on this BZ https://bugzilla.redhat.com/show_bug.cgi?id=1097160, since it pointing to same view 'storage_domains' What tab/subtab generates this query? as I mention above the by profiler results it looks like it triggered by 'vdsupdateruntimeinfo' (In reply to Eldad Marciano from comment #4) > as I mention above the by profiler results it looks like it triggered by > 'vdsupdateruntimeinfo' I missed that sentence in comment 1. Sorry. Can you share the stacktrace please? This doesn't make sense to. actually there is a stacktraces from the first time i have faced the bug. (In reply to Eldad Marciano from comment #6) > actually there is a stacktraces from the first time i have faced the bug. And they are where? Sorry, Adding profile export. Created attachment 986654 [details]
profile export
tested on VT13.7, query runs x2 faster |