After overnight idle time, the first call to a parks-department Oracle Function takes several seconds, while immediate follow-up calls return much faster. What explains the slow first invoke?
Select an answer to reveal the explanation.
Short Explanation
Like opening a closed community center before the first visitor, the platform must spin up execution space after idle time. That cold start can take seconds; reuse of the same infrastructure makes later calls hot and snappy.
Full Explanation
Oracle Functions provisioned-concurrency documentation notes that the first invocation, or the first after idle time, provisions execution infrastructure—a cold start that can take seconds. Subsequent invokes that reuse that infrastructure are hot starts and are typically much faster. Idle reuse is automatic platform behavior; it is not something you code into the FDK.