New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
take us up through expected auto RDS updates #4391
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #4391 +/- ##
=============================================
+ Coverage 69.12% 69.16% +0.03%
Complexity 3661 3661
=============================================
Files 266 266
Lines 15096 15096
Branches 1647 1647
=============================================
+ Hits 10435 10441 +6
+ Misses 3890 3884 -6
Partials 771 771
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Weird, 11.12 is halfway better than develop but worse than 11.8 |
11.10 |
11.9 FFS with JDBC 23
|
think bitbucket is having issues (workflow-integration-tests) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'll need to reset dev back to 11.x. PG probably doesn't allow that; we may need to just spin up a new instance of RDS.
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Depends on whether we figure this out and are still stuck on postgres 11 when dockstore 1.12 comes out. One known unknown, is the testing slowdown actually seen in real life on AWS RDS or is https://ucsc-cgl.atlassian.net/browse/DOCK-1854 just due to the jdbc driver problem? |
#4347 was only seen locally. I think the verification of #4338 shows there was no regression in prod. I'll try #4347 again using these changes to see if it fixes it. |
this is newer than what aws rds is running (11.10) , companion to #4388
this maintains performance as seen with 11.8 and with JDBC 42.2.19 but this is with JDBC 42.2.23
Note that "Auto minor version upgrade" is on and will automatically take us to 11.12 at some point anyway
pgjdbc/pgjdbc#2180 explains the pain we ran into with JDBC 42.2.21 but doesn't explain the full problem with postgres 12/13
background benchmarking at https://app.slack.com/archives/CEGMXHBHT/p1628280502020200