Grouper Developers Forum

[Michael Douglass <>]

I mentioned this a long time ago - I tried stepping through the entire 
call but could not find the issue.

I don't believe it's a performance issue as such with hsqldb. I tried 
the queries directly and they return almost immediately.

It happens in a number of places - I worked on developing an app using 
grouper and debugging was a pain because of these long delays

I'd be inclined to suggest moving to h2.

It will certainly look like a performance issue - the hangs are for 
about 16 seconds or so


On 10/16/18 14:00, Black, Carey M. wrote:
> 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 
> membership1_
> where membership1_.owner_group_id=? and membership1_.field_id=?
>         and membership1_.member_id=member0_.id and 
> membership1_.immediate_mship_enabled='T'
>
> 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.