...
[11:50:23 CDT(-0500)] <dmccallum54> it's worth it
[12:03:04 CDT(-0500)] <TonyUnicon> I think I can run to the server and write down the recent activity faster than it takes to render on this screen
[12:04:34 CDT(-0500)] <TonyUnicon> could be that was my map student and he has about 100 maps
[12:04:43 CDT(-0500)] <TonyUnicon> map test student*
[12:08:32 CDT(-0500)] <dmccallum54> this might be one reason god invented database indexes
[12:10:31 CDT(-0500)] <TonyUnicon> I'd venture to guess its more the hibernate bloat than table scanning
[12:11:10 CDT(-0500)] <dmccallum54> outer joins dont speed things up?
[12:12:18 CDT(-0500)] <TonyUnicon> I'd have to see how that recent activities are being loaded, it could be easier to use a custom result set for that panel with HQL so it doesn't load the kitchen sink
[12:12:52 CDT(-0500)] <dmccallum54> (the outer joins comment was another hilarious joke)
[12:13:05 CDT(-0500)] <TonyUnicon> it does't even hit me
[12:13:07 CDT(-0500)] <TonyUnicon> didnt*
[12:13:19 CDT(-0500)] <TonyUnicon> yes outer joins are of course slower
[12:14:17 CDT(-0500)] <js70> recent actitivies can can definitely use a look, Made the assumption that any individual would not have that much activity so pulling mostly everything. could definitely reduce that.
[12:14:25 CDT(-0500)] <dmccallum54> i'm sure there's a bajillion of them on anything that has a Person association