This API can have a bunch of overloads in the open command, but what happens under it is almost the same. If you do not switch to a completely different API or another db, there is no way to "speed up the process."
The only thing you can do is mitigate the problem by moving the connection open to any other part of the application’s life cycle, when the user may not notice or delay the delay.
One trick that is widely used is to implement this small hand in order to complete your initialization while the user screen is displayed. The screensaver may have some fancy graphics and text to “entertain” the end user. You will even see that the pop-up screen is updated with what the application does at this particular time. Not very useful, but may be interesting enough for the user to distract from the delay.
I did this once when users complained about the initialization step for too long. After I posted the change, end users vowed that the application works much better. This is actually not the case. I only manipulated perception.
Paul sasik
source share