Bug 806477 - RFE: Review use of OrderBy annotations in the domain model
Summary: RFE: Review use of OrderBy annotations in the domain model
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Database
Version: 4.3
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: rhq-perf
TreeView+ depends on / blocked
 
Reported: 2012-03-23 21:50 UTC by Jay Shaughnessy
Modified: 2022-03-31 04:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 641045 0 low CLOSED ordering of elements in a property list is not persisted correctly 2021-02-22 00:41:40 UTC

Internal Links: 641045

Description Jay Shaughnessy 2012-03-23 21:50:06 UTC
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
value.

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 15:51:27 UTC
priority = medium, no target release, per BZ triage (crocuh, asantos, mfoley, loleary)

Comment 2 Charles Crouch 2012-03-27 02:37:26 UTC
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.