Bug 1074705
Summary: | Look at caching minhash xor values | ||
---|---|---|---|
Product: | [Community] PressGang CCMS | Reporter: | Matthew Casperson <mcaspers> |
Component: | CCMS-Core | Assignee: | Lee Newson <lnewson> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 1.4 | CC: | cbredesen, lnewson |
Target Milestone: | --- | ||
Target Release: | 1.5 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-05-01 21:39:59 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Matthew Casperson
2014-03-10 22:43:45 UTC
This should also be applied to the Topic XML factory, as it also produces the same slow query. Fixed in 1.5-SNAPSHOT build 201404111431 The MinHashXOR select all query is now cached upon first use in the CacheEntityLoader class. All references of getting all the MinHashXOR's are now accessed via the CacheEntityLoader and when the MinHashXORs are recalculated the cached values are invalidated. Additionally I've also optimized how minhashes are calculated to save processing time by removing logic that can be done once instead of for every MinHashXOR value. Note: This version is currently live on the test/development server. I changed the HashMap in CacheEntityLoader to a ConcurrentHashMap. From what I can tell concurrent read and write access to a HashMap can lead to unpredictable results. |