Hi Community,
I have installed ORDS 19.4 on Tomcat 9.0.34 on AWS RDS Oracle EE 12c.
When fetching large number of rows, ORDS is very slow.
I have already change entries in defaults.xml for JDBS maxlimitconnections:
<entry key="jdbc.DriverType">thin</entry>
<entry key="jdbc.InitialLimit">3</entry>
<entry key="jdbc.MinLimit">1</entry>
<entry key="jdbc.MaxLimit">20</entry>
<entry key="jdbc.MaxStatementsLimit">20</entry>
<entry key="jdbc.InactivityTimeout">1800</entry>
<entry key="jdbc.statementTimeout">900</entry>
<entry key="jdbc.MaxConnectionReuseCount">1000</entry>
But there is no improvement.
When changing the page_size from default 20 to 500 the time for fetching > 300.000 records comes from 11 hours to 1 hour.
But still it is not acceptable and we need further improvements.
The authentication is set on 'Basic Authentication', and ORDS service creates for every feched page a new connection/authentication.
I wonder if this could be changed by AUTH2 authentication + storing the token for the secret client key? How should I implement this?
Can we use connection pooling on Tomcat level?
I would very much appreciate any feedback on above questions.
Many thanks,
Kind regards,
Johan Hoste