Heroku request timeout

[epoberezkin]

Heroku request timeout

[prnewman]

@rtyley Thanks for the feedback. I'll update if things change as more users comply.

This hiccup notwithstanding, gu:who has been extremely helpful. Thank you!

[prnewman]

We get the same application error in an organization with 273 github users.

[rtyley]

@Nick-Smith has mentioned this issue as well - presumably you work together @prnewman ?! He said:

Basically, it looks like the request times out. I think the audits are being run successfully but the results page never renders because it has to wait too long. We have >250 users so it might just be an issue of too many users to churn through in the given time? You might be able to fix it by parallelizing the audit for each user.

Sorry to hear about the problems you've been having. Nick's idea of parallelizing the audit by user sounds reasonable, the code you'd want to try changing would be:

https://github.com/guardian/gu-who/blob/19d779dd16/app/lib/OrgSnapshot.scala#L111-L137

We have ~190 users and the job doesn't time out - usually the first run is the worst while all the GitHub calls are getting cached. We're also using a legacy Heroku dyno which may actually be better performing, but not an option for you:

It will also run slower if there are lots of non-compliant users - we're in the happy position of having 100% compliance at the Guardian, so the check runs pretty fast. You may want to run gu:who locally on a laptop for a few days (getting the number of non-compliant users to decrease) before switching over to Heroku.

I'm afraid @lindseydew & I are pretty busy right now, we haven't much time for maintenance on gu:who!

[Nick-Smith]

@rtyley Awesome, thanks for the help Roberto! And yes, @prnewman is a colleague of mine.
It seems like the service is actually working, it's just the UI that is timing out.

Hopefully once the service has warmed up and most of our users are compliant the UI will start working.