grouper-dev - [grouper-dev] RE: Possible performance issue with HSQLDB...
Subject: Grouper Developers Forum
[grouper-dev] RE: Possible performance issue with HSQLDB...
- From: "Black, Carey M." <>
- To: "Hyzer, Chris" <>
- Cc: "" <>
- Subject: [grouper-dev] RE: Possible performance issue with HSQLDB...
- Date: Thu, 1 Nov 2018 12:01:16 +0000
- Accept-language: en-US
- Authentication-results: spf=pass (sender IP is 22.214.171.124) smtp.mailfrom=osu.edu; internet2.edu; dkim=pass (signature was verified) header.d=osu.edu;internet2.edu; dmarc=pass action=none header.from=osu.edu;
- Authentication-results-original: spf=none (sender IP is ) ;
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
Oh.. I forgot to add something to this thread... Later we discovered this
If you are using the UI with a "GrouperSystem" account then the behavior is
not to bad at all. ( Still slow, but not painful.)
If you also use the system as a "normal user" then it becomes not usable with
any complexity in the system. UI timeouts, 10-30 minute hook completion times
(yes, using Async work from in uI based hooks to avoid the UI timeout.)
So if you run tests as "GrouperSystem" then you will likely avoid some of
this. But that likely does not work for "user centric tests".
From: Hyzer, Chris
Sent: Wednesday, October 31, 2018 6:28 PM
To: Black, Carey M.
Subject: RE: Possible performance issue with HSQLDB...
Yes its hibernate. Haven't seen a problem with this one...
From: Black, Carey M.
Sent: Tuesday, October 16, 2018 2:01 PM
To: Hyzer, Chris
Subject: Possible performance issue with HSQLDB...
Chris, (et. al.)
I have a test instance that is currently still using the HSQLDB. ( I know...
I am going to reset the env and move to a "real DB" ... soon...)
But I found that when a group is being added as a member of another group
this SQL takes a very long time to execute:
select member0_.id as id1_24_,
member0_.hibernate_version_number as hibernat2_24_,
member0_.subject_id as subject_3_24_,
member0_.subject_source as subject_4_24_,
member0_.subject_type as subject_5_24_,
member0_.context_id as context_6_24_,
member0_.subject_identifier0 as subject_7_24_,
member0_.sort_string0 as sort_str8_24_,
member0_.sort_string1 as sort_str9_24_,
member0_.sort_string2 as sort_st10_24_,
member0_.sort_string3 as sort_st11_24_,
member0_.sort_string4 as sort_st12_24_,
member0_.search_string0 as search_13_24_,
member0_.search_string1 as search_14_24_,
member0_.search_string2 as search_15_24_,
member0_.search_string3 as search_16_24_,
member0_.search_string4 as search_17_24_,
member0_.name as name18_24_,
member0_.description as descrip19_24_
from grouper_members member0_ cross join grouper_memberships_all_v
where membership1_.owner_group_id=? and membership1_.field_id=?
and membership1_.member_id=member0_.id and
Maybe this is the "performance issue" that you have seen from time to time in
the test scripts?
( "cross join" sounds.... like a bad idea on any system of any size.)
Maybe this is just a hibernate on HSQLDB issue? Maybe not?
Hope that helps.
- [grouper-dev] RE: Possible performance issue with HSQLDB..., Black, Carey M., 11/01/2018
Archive powered by MHonArc 2.6.19.