Fantastic read.

In terms of connection pool sizing, I highly recommend the work of Toon Koppelaars. (reference: neooug.org/gloc/Presentations/2019/Koopelears_Con…)

which recommends pool sizing as:

min = max = initial.

The TL;DR rationale from the presentation for that recommendation is:

• unused pool sessions are idle, they do nothing and consume minimal resources because the last thing pool-based apps do is free their resources when they give back a connection. If they dont, then you've got an app bug not a connection pool config issue.

• the max size setting (by definition) is what you are prepared to let your server handle without undue stress, so why would you pick a min/initial less than that, because to do so means yours apps incurring the cost of creating a connection pseudo-randomly. That makes response times variable.

The article 'Configuration Changes to Make after Installing ORDS Standalone' is a vital guide for database administrators and developers. It provides essential tips on optimizing ORDS (Oracle REST Data Services) post-installation, ensuring efficient and secure operations. This piece is invaluable for those looking to enhance their ORDS configurations for better performance.crema-articulara.com/ostyhealth-forum

Excellent post Jon.

I'd like to see the logs go to /var/log/ords instead of /etc/ords as that's where logs go on a Unix/Linux system and (quite often), the /var/log partition is separate so that if it fills up only logging stops and not the whole server.