Reuse oci_connect() connection identifier through different apache-php requests or oci_pconnect() conection pooling

43
May 15, 2018, at 1:30 PM

I'm facing this problem. A client call an API one method each time, API use at least one oci_connect() for each request. There are hundreds of methods and thousands of concurrent users (Sometimes this number is much higher). As I understand, oci_connect() is useful since there are many concurrencies, because oci_pconnect() will become less useful as the number of concurrent users increases. But oci_connect() is too expensive. If I could reuse oci_connect() resource through different requests, I could avoid connecting to database each time a client make a request and I can perform my own connection cache. Is there a way to do this, any idea? Maybe I could use both connections but how do I choose?

I know this problem is easy to solve changing the design and put all requests in the same thread in some way, but it's not possible because of other requirements.

READ ALSO
Form.php file not sending through inputted data

Form.php file not sending through inputted data

I have been working on a form in a php fileAs you'll see from the code below I have written everything in a PHP file including the form tag

21
multidimensional array structure from database PHP

multidimensional array structure from database PHP

I want to create a multidimensional array from database resultsI have a table with teams and a table with results, that include the team id, and an event type with the results for each

29
Google analytics error caused by shopify app

Google analytics error caused by shopify app

I have app on shopify and it causes error because google follow app links (App proxy) links

40