Bug 806477 - RFE: Review use of OrderBy annotations in the domain model
RFE: Review use of OrderBy annotations in the domain model
Status: NEW
Product: RHQ Project
Classification: Other
Component: Database (Show other bugs)
All All
medium Severity medium (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
Depends On:
Blocks: rhq-perf
  Show dependency treegraph
Reported: 2012-03-23 17:50 EDT by Jay Shaughnessy
Modified: 2012-03-26 22:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jay Shaughnessy 2012-03-23 17:50:06 EDT
We have many instances of OrderBy annotation in our domain objects. And
most of then are defaulting to the ID field, typically just the sequence

I'm not sure why we use these but in effect they cause in-memory
sorting by hibernate on the fetched data.  This of course slows things
down. A quick look shows that most are probably not a big deal given
low cardinality, but a few look interesting.  In general, if not needed
they just add confusion, along with a possibe perf hit.

One in particular to look at is Resource.childResources.
Comment 1 Mike Foley 2012-03-26 11:51:27 EDT
priority = medium, no target release, per BZ triage (crocuh, asantos, mfoley, loleary)
Comment 2 Charles Crouch 2012-03-26 22:37:26 EDT
Another in-memory issue similar to bug #620603

Note You need to log in before you can comment on or make changes to this bug.