Skip to Content.
Sympa Menu

grouper-users - [grouper-users] Anyone using cloud RDBMS with on-prem Grouper?

Subject: Grouper Users - Open Discussion List

List archive

[grouper-users] Anyone using cloud RDBMS with on-prem Grouper?

Chronological Thread 
  • From: Greg Haverkamp <>
  • To:
  • Subject: [grouper-users] Anyone using cloud RDBMS with on-prem Grouper?
  • Date: Tue, 17 Apr 2018 21:46:59 -0700
  • Ironport-phdr: 9a23:ppxdBx+W6OYo3f9uRHKM819IXTAuvvDOBiVQ1KB41+4cTK2v8tzYMVDF4r011RmVBd6ds6oMotGVmpioYXYH75eFvSJKW713fDhBt/8rmRc9CtWOE0zxIa2iRSU7GMNfSA0tpCnjYgBaF8nkelLdvGC54yIMFRXjLwp1Ifn+FpLPg8it2O2+55Pebx9UiDahfLh/MAi4oQLNu8cMnIBsMLwxyhzHontJf+RZ22ZlLk+Nkhj/+8m94odt/zxftPw9+cFAV776f7kjQrxDEDsmKWE169b1uhTFUACC+2ETUmQSkhpPHgjF8BT3VYr/vyfmquZw3jSRMsPsTbAwRD+s8aFlRhH1gysDLjI17X3bhsl2galGohyuugZ/zpbUbo+bN/RwY73Tcs8BSGVbQspcTTZMDp+gY4YNCecKIOZWr5P6p1sLtRawBBOsC/3gyjRVhHH5x7M63Po7EQHFxgMgGsoOu2nTodX6LqgSUfq6zLfWwjXZbPNZwzL96JDTfxAluv6MWah8ccXWyUkxDg7IiEibp4/9Pz6Ny+gBrWuW4/BuWO61hGMrtht9rzmsy8s0lIXFmoYYxkrH+Ch52oo5O8C0RU1hbdOlFJZdsTyROZFsTcM4WW5ovT43yr0Ytp6/eygH0JonyADRZvCdd4iH+RbjWPyeITd/mnJpYLO/hxCs/ki80uDwS9e43VVQoidLiNXBuW0B2wbS58WEUvd9+12u2TeL1wDd8OFEJkU0mLLUK5E7wr4/jIQTvlrZHi/1gkr2ibeWe14g+uez7+TreLrmppiCN4NskAHxLrwumtCjAeQ/KgUOUHKb+eOh1L3740L5WqxGjuAtkqbHqpDaPt8Wpqq4Aw9OzoYj8AizAy2n0NQegXkIMkhFeBSZgIj1JV3COu73AuqigwfkrDA+yOrBI6XsGNDQNXXZi5/ge6pw8UhR1FB1wNxCtLxODbRUD+j+VQfRvcLVFBwwNhT8l+nuCNxj25kdUGeXKquTNOXdtkHetbFnGPWFeIJA4GW1EPMi/fO7yCZhlA==

My deployment progress has been literally slowed, and I'm trying to figure out if there's something I'm just doing wrong.

I've generally had pretty good luck with AWS RDS (though with Postgres), and we run a couple of services off of it.  Our plan was to deploy the Grouper DB to AWS RDS (MySQL) while running Grouper on-prem, at least until we work out our desired strategy for pushing everything out.  

However, we've found Grouper to be ridiculously slow in this model.  Slow enough that it makes it difficult to try to get anything done with it.

Today I spent the day poking, prodding, resizing, creating new resources, etc., all which seem to indicate that perhaps the Grouper DB is not well-suited to even minimal latency.  I'm wondering if anyone else has attempted this and found otherwise?

At this point, I've tried AWS RDS MySQL (5.7).  With my load, gsh takes about a minute to display its prompt.  This seems to be the case regardless of RDS instance size (bumped to get "Network Performance" from "Medium" to "High", General SSD storage size (bumped it up to 100 GB to try to get the performance wins), etc.  I also converted to Amazon Aurora, in an attempt to see if it could be that.  However, performance remained basically the across all attempts.  Around 1 minute to get to the gsh prompt and around 1-2 seconds to findSubject().

Then, I decided to try a quick benchmark.  I cranked up a MySQL 5.7 Docker on my desktop, loaded up my data, and pointed my Grouper instance at it.  gsh appeared in around 10 seconds, and the findSubject() returned almost immediately.

Deciding I'd give one last shot at not having to run my own database, I cranked up MySQL at Google and loaded the data.  It returns faster, but only about 20% faster than AWS.  (It's perhaps not coincidental that my ICMP RTTs around about 20% faster to Google than to AWS.)

I'm guessing this is likely in the nature of Grouper, and that perhaps it's just running so many queries that 20 ms per query starts to add up.  Does that seem about right?


Archive powered by MHonArc 2.6.19.

Top of Page